System and method of autonomous restore point creation and restoration for luminaire controllers

ABSTRACT

A method ( 3600 ) and system ( 2800, 2900, 3000, 3100 ) autonomously create a restore point for a luminaire controller ( 2810, 3110 ) and restore it to proper operation when required. The luminaire controller operates by using first operating software having a first software image, and receives a second software image of second operating software. The luminaire controller communicates the first software image to a first device ( 2820, 3120 ) connected to the luminaire controller via a communication network ( 2805, 3105 ), installs the second operating software, and performs a self test of the luminaire controller. If the luminaire controller fails the self test, the luminaire controller requests via the network that the first device transfer the first software image to the luminaire controller via the network, receives the first software image, installs the first operating software, and reverts to operation with the first operating software.

CROSS-REFERENCES TO RELATED APPLICATIONS

This patent application claims priority from Indian patent application4854/CHE/2014, filed on Sep. 29, 2014, and European patent application14195337.2, filed on Nov. 28, 2014, the entirety of which applicationsis hereby incorporated by reference as if fully set forth herein.

TECHNICAL FIELD

The present invention is directed generally to the management ofenvironmental conditions within physical structures. More particularly,various inventive systems and methods disclosed herein relate toadjusting environmental conditions such as lighting conditions,temperature, and humidity based on automatically and manually generatedrequests. Some inventive systems and methods disclosed herein alsorelate to monitoring energy consumption and the utilization of resourceswithin physical structures, and adjusting system behavior accordingly.

BACKGROUND

Digital lighting technologies, i.e. illumination based on semiconductorlight sources, such as light-emitting diodes (LEDs), offer a viablealternative to traditional fluorescent, HID, and incandescent lamps.LEDs offer many advantages, including controllability, high energyconversion and optical efficiency, durability, and lower operatingcosts. Recent advances in controllable LED technology have providedefficient and robust full-spectrum lighting sources that enable avariety of lighting effects in many applications.

Alongside the development of controllable LEDs, rapid developments havebeen made in the area of sensor technologies. Sensors today are not onlyable to effectively measure natural illumination and occupancy, but havealso become significantly smaller, and therefore able to easily fitinside small devices, including devices housing controllable LEDs andcameras. For example, existing natural illumination based lightingcontrol systems are able to employ individually controllable luminaireswith dimming ballasts as well as one or more natural illumination photosensors to measure the average workplane illumination within a naturallyilluminated space. In such systems, one or more controllers, in order torespond to daylight egress and maintain a minimum workplaneillumination, may monitor the output of one or more photosensors andcontrol illumination provided by the luminaires.

More recently, innovations in the realms of wireless communication andsmart mobile devices have launched a generation of smart phones andtablet computers with unparalleled mobility and computational power. Forexample, mobile smart phones with access to applications on cloudservers are able to gather, and process data from their immediateenvironments in real time. Additionally, location-based services allowfor the customization of information delivered to mobile devices. Smartmobile devices, used in conjunction with controllable LEDs andappropriate sensors can therefore be used to customize illumination inphysical spaces in real time.

Today, two other significant technological developments present evengreater opportunities for innovations in the area of environmentalmanagement and control: Power over Ethernet (PoE) and Coded Light (CL).PoE allows for the delivery of electrical power along with data over asingle cable to devices such as lighting devices, IP cameras or wirelessaccess points. The advent of PoE technology makes it feasible to powerdevices in remote locations within building structures, by significantlyreducing the need for electricians to install conduit, electricalwiring, and outlets. Unlike other devices, the potential location of aPoE device is not limited based on the placement of AC outlets within astructure. For example, PoE allows wireless LAN access points to beplaced on ceilings for more optimal RF reception.

CL technology can be used to embed unique identifiers, or codes, intothe light output from different light sources. Using these identifiers,the light emanating from a specific light source can be differentiatedeven in the presence of illumination contributions from multiple otherlight sources. CL can therefore be used to identify and locateindividual light sources and devices relative to other such sources anddevices. The use of light as a means for device identification, locationand communication opens the door to innovative systems and methods formanaging environmental conditions by allowing fine-grained interactionsbetween devices such as individually controllable LEDs, sensors, andcontrol devices such as smart phones that were not previously feasible.

Existing systems and methods for managing environmental conditionswithin physical structures do not simultaneously leverage the benefitsof the aforementioned technologies. Some existing systems merely utilizecontrollable LEDs and sensors to automatically control lighting in areassuch as offices and living rooms in response to changes in, for example,occupancy and natural illumination in the area. Other existing systemsprovide mobile applications that allow users to remotely control thebehavior of lighting devices within such spaces. But no existing systemprovides the hardware and software infrastructure necessary toeffectively manage the complex interaction of a multitude of PoE and CLenabled devices (e.g. lighting devices and HVAC appliances), smartmobile controllers, wall-mounted controllers, and sensors monitoring theactivity and environmental conditions in large facilities such as officebuildings. The effective management of environmental conditions withinsuch spaces poses several unique technological challenges discussedbelow. The embodiments disclosed herein offer solutions to these andother challenges.

Large office buildings or other large commercial buildings usually haveareas that are used for a variety of purposes. An office building mayhave conference or meeting rooms, large open-plan spaces with amultitude of cell offices, hallways, cafeterias, and auditoriums. Someof these areas may be generally used for group discussions or largepresentations (e.g. conference rooms and auditoriums), while others maybe used for individual work (e.g. cell offices). Given their differentpurposes, some modes of controlling environmental conditions (e.g.personalized control) may therefore be better suited to some areas (e.g.cell offices) rather than other areas (auditoriums and cafeterias).Unlike single family homes or apartments, large office buildings alsoaccommodate sizable numbers of individuals, often in close quarters.These individuals may have differing and often conflicting interestsregarding environmental conditions they wish to create in the spacesthey occupy. When the same space is being used by different individuals,therefore, it is crucial to resolve conflicting requests to adjustenvironmental conditions in a meaningful rather than arbitrary way.Moreover, the amount of control a user may be allowed to exert in anyspace may depend on his or her role within an organization. It may beproblematic, for example, if an employee attending a presentation in alarge auditorium is able to use an application on his/her smart phone tochange lighting conditions in the whole auditorium at any time.

Managing environmental conditions inside large structures thereforeinvolves effectively prioritization and coordinating the potentiallynumerous concurrent control requests arising from a large number ofstationary and mobile controllers representing a variety of users. Theserequests would need to be successfully routed to appropriate lightingdevices and HVAC appliances in order to produce the requested changeswithin a time frame that also reasonably meets user expectations.

The variety of lighting and HVAC devices/appliances that typicallyoperate in large buildings presents another fundamental challenge to anysystem for controlling environmental conditions. These devices do notall produce data in the same format, nor do they all supportcommunications over the same protocols. Yet, under many circumstances,it may be necessary for these devices to communicate with each other,directly or through intermediate modules. To ensure that devices areable to communicate with each other, either direct or indirectly, whennecessary, systems for managing environmental conditions will need toprovide the means necessary for such communication to occur.

Yet another challenge facing systems for managing environmentalconditions is that once the numerous sensor, control and other devicesand system components are installed and operational within a largestructure, new devices designed to produce or receive data in formatsnot supported by the system become available. For systems for managingenvironmental conditions in large structures, this problem is even moreacute since these systems likely utilize many more types of devices ascompared to simpler systems for managing environmental conditions insmaller spaces such as residential homes. Such larger-scale systems willneed to be adaptable enough to accommodate the use of such new devicesin order to be able to take advantage of improvements in technology. Asa result, it is very important that these systems are designed to beeasily extensible to accommodate new devices and technologies so thatthey may be integrated into the system with minimal effort and withoutundue disruption to the operation of the system.

Although existing systems for managing environmental conditions inrelatively smaller spaces, such as in apartments or homes, may monitordevice usage for a variety of reasons, the amount of such usage datagenerated by such systems is relatively small. By contrast, a largebuilding or structure will likely generate large amounts of usage datadue to the large numbers of devices (lighting and HVAC devices andsensors) in these structures. This data will need to be gathered,categorized and analyzed in order for the system to gain any usefulinsights for use in, for example, fine tuning existing energyconservation strategies. In order to make good use of the data, withoutoverwhelming or degrading the performance of the system as a whole, asystem for managing environmental conditions in a large structure needsto be designed to accommodate the potentially large influx of usagedata. Some such systems may be designed such that the management ofusage data is significantly decentralized. For example, device usagedata gathered from different floors of a building may be managed byseparate modules using separate data storage facilities.

Lastly, while there are privacy issues surrounding the management ofusage data in smaller settings, the issues are not comparable in scaleto the privacy issues that must be dealt with in much larger settings.For example, an environment management system designed for a residentialsetting such as an apartment may only have a few individual users whosepersonal information needs to be handled in a manner that does notcreate risk of disclosure to unintended parties. By contrast, a largeentity occupying a large office space may have hundreds of users whofrequent the space, accessing various system components via a multitudeof user interfaces on a variety of devices, including their personalmobile devices. For example, the use of personal mobile computingdevices as controllers for CL enabled lighting and other devices canresult in, for example, useful but sensitive associations between auser's identity and particular frequented spaces. Accordingly, thedesign of environment management systems for deployment in largestructures needs to provide for the implementation of strategies toprevent both unauthorized access to such sensitive information fromwithin the system itself (e.g. one system user accessing information onthe whereabouts of another), and from outside the system (e.g. cybersecurity breaches exposing such sensitive information to the outsideworld).

Furthermore, in large and complex illumination and environmentalmanagement systems, a large number of luminaries and other devices maybe deployed. Over time, new luminaries and other devices may be added tothe system, and existing luminaires or other devices may be replaced orupgraded with new capabilities, functions, or configurations. In thatcase, it is possible that some “legacy” devices may exist in a systemwhich may not operate properly, or may cease to operate altogether, whenit is attempted to upgrade them to support new capabilities, functions,or configurations. Particularly when a system is large or complex, itmay not be immediately apparent to the owner or operator of the systemthat this has occurred so that corrective actions may be taken withrespect to the malfunctioning or non-operating luminaries and otherdevices. Furthermore, human intervention in such cases may incursignificant costs and/or inconvenience, and so this is not always anoptimal solution.

No existing system for managing environmental conditions providessolutions to at least the aforementioned challenges. The systems andmethods presented below provide solutions designed to address these andother challenges.

SUMMARY

Various embodiments are directed herein to systems and methods formanaging environmental conditions within a physical structure, in orderto address the problems set forth in the previous section. This sectionpresents a simplified summary of some of these methods and systems inorder to provide a basic understanding of various system components, theinteraction between such components, and the various steps involved invarious embodiments. This summary is not intended as an exhaustiveoverview of all inventive embodiments. The system components and methodsteps described in this section are not necessarily critical componentsor steps. The purpose of this summary section is to present an overviewof various concepts in a more simplified form, as an introduction to thedetailed description that follows.

Various embodiments disclose a system for managing environmentalconditions within a physical structure. The system comprises at leastone commissioned unit configured to transmit a coded light signalcomprising one or more identification codes, and an environment controldevice configured to receive the coded light signal from the at leastone IP luminaire, to detect user input indicating one or more preferredenvironmental conditions, and to transmit an environment control requestcomprising the one or more preferred environmental conditions. Invarious embodiments, the aforementioned system also comprises one ormore processors executing an environment manager module configured toreceive the environment control request, to generate an environmentcontrol command using the control request, and to transmit theenvironment control command to the commissioned unit.

In various aspects, the environment manager module is configured tomonitor usage of the at least one commissioned unit, and to provide oneor more user interfaces for visualizing usage data associated with thecommissioned unit. In some aspects, the at least one commissioned unitis configured to receive power from a PoE switch, and comprises aplurality of IP luminaires, each IP luminaire being communicativelyconnected with one or more sensors, one or more controllable lightsources, and a luminaire control module. The one or more sensors areconfigured to detect at least one of: motion, occupancy, sound, and thepresence of one or more gases, or measure at least one of: illumination,humidity, and temperature.

In some other aspects, the environment manager module is configured todetermine at least one of: whether a type of control associated with thereceived environment control request is enabled with respect to thecommissioned unit, the type of control comprising personal control; andwhether the received environment control request conflicts with anotherhigher-priority control request associated with the commissioned unit.

In many embodiments, the aforementioned system further comprises one ormore processors executing a commissioning module for associating one ormore devices with the system for managing environmental conditions. Theassociating comprises localizing one or more devices. The localizationcomprises mapping each device to at least one physical location withinthe physical structure. The associating also comprises associating, in amemory, at least one of the one or more devices with a firstcommissioned unit, and linking the first commissioned unit with a secondcommissioned unit, the linking comprising associating, in a memory, thefirst and second commissioned units. In some aspects of theaforementioned system, the first memory is accessible to at least theone or more devices associated with the first commissioned unit, and thesecond memory is accessible to at least the one or more devicesassociated with the first and second commissioned units.

In some aspects, the commissioning module is configured to update atleast one memory accessible to the environment manager module, using atleast one value representing a parameter associated with the at leastone of the one or more devices, the first commissioned unit or thesecond commissioned unit. In some other aspects, the commissioned unitof the aforementioned system that is configured to receive theenvironment control command, is further configured to alert anycommissioned units with which it is linked, of changes in its ownoperational status and changes in the status of a zone with which it isassociated. The alerting may involve direct or synchronous modes ofcommunication, where the commissioned unit transmits signals indicativeof the changes to each of its linked commissioned units. The alertingmay also involve more indirect or asynchronous modes of communication.For example, the commissioned unit may inform an executing module of itsoperational status change; the executing module may access a memory todetermine which other commissioned units are linked to the commissionedunit; and the executing module may thereafter notify each of the linkedcommissioned units of the status change.

In various aspects, the aforementioned system also comprises one or moreprocessors executing a gateway module that is communicatively connectedto a commissioning module and to an environment manager module. Thegateway module is configured to receive an environment control commandfrom one of: the environment manager module, the commissioning module, adevice and a commissioned unit. And the gateway module is alsoconfigured to convert the control command into a format suitable for atleast one of: a destination device or a destination commissioned unit.

In some aspects, the gateway module is further configured to receivemonitoring data comprising the operational status and energy consumptiondata from one or more commissioned units or devices, and to convert thereceived monitoring data into a format suitable for the environmentmanager module.

Various embodiments disclose another system for managing environmentalconditions within a physical structure. The system comprises a sensor ina designated zone within the physical structure configured to producedata indicative of at least one of: motion, occupancy, sound, thepresence of one or more gases, illumination, humidity, and temperature.The system also comprises a commissioned unit comprising a gatewaymodule communicatively connected to at least the sensor and anenvironment manager module. The commissioned unit is configured toreceive the data produced by the sensor, to determine that the sensordata represents a status change associated with the designated zone, andto update one or more memories accessible to the environment managermodule in accordance with the data representing the status change.

Some embodiments disclose a system for managing environmental conditionswithin a physical structure. The system comprises at least onecommissioned unit configured to transmit a first signal comprising oneor more identification codes. The system also comprises an environmentcontrol device configured to receive the first signal from the at leastone commissioned unit, to detect user input indicating one or morepreferred environmental conditions, and to transmit an environmentcontrol request comprising the one or more preferred environmentalconditions. Further, the system comprises one or more processorsexecuting an environment manager module configured to receive theenvironment control request, to generate an environment control commandusing the control request, and to transmit the environment controlcommand to the commissioned unit.

Some embodiments disclose a method for identifying devices forassociation as a single commissioned unit within a system for managingenvironmental conditions. The method comprises a first step of a firstplurality of devices, each transmitting a coded light signal comprisinga unique identification code. In a second step, a mobile device receivesthe coded light signals from the first plurality of devices, andtransmits a commissioning request comprising unique identification codesof a second plurality of devices that are located in a region proximateto the mobile device, the second plurality of devices comprising one ormore devices from the first plurality of devices. In a third step, acommissioning module receives the commissioning request and associates,in a memory, the second plurality of devices with a first commissionedunit.

Various embodiments disclose a method for managing environmentalconditions within a physical structure comprising a plurality of linkedcommissioned units. The method comprises a first step of one or moreoccupancy sensors producing data indicating that a designated zone hastransitioned from an unoccupied state to an occupied state (910B). Themethod also comprises a second step of a first one or more luminairesassociated with a first one of the plurality of linked commissionedunits, producing a background level of illumination within apredetermined reaction period following the production of the sensordata. A third step involves the first one of the plurality of linkedcommissioned units transmitting data indicative of the state change ofthe designated zone (930B). And a fourth step involves at least a secondone of the plurality of linked commissioned units receiving the dataindicative of the state change, and causing at least a second one ormore luminaires to alter illumination. In some aspects, the second oneof the plurality of linked commissioned units or the at least second oneor more luminaires accesses a memory storing lighting scene informationprior to the at least second one or more luminaires alteringillumination.

Many embodiments disclose yet another method for managing environmentalconditions within a physical structure comprising a plurality of linkedcommissioned units and one or more occupancy sensors. The methodcomprises a first step of making a first determination, based onoccupancy data produced by the one or more occupancy sensors, that adesignated zone has transitioned from an occupied state to an unoccupiedstate. The method also comprises a second step of monitoring additionaloccupancy data produced by the occupancy sensors for at least part ofthe duration of a hold period, and making a second determination as towhether or not the designated zone remained in the unoccupied state forthe entirety of the hold period. The method includes a fourth step ofaccessing a memory to identify at least one of the plurality of linkedcommissioned units associated with the designated zone, and a fifth stepwherein, based on the result of the second determination, one or moreluminaires of the at least one of the plurality of linked commissionedunits fades to a first lower level of illumination over a first graceperiod that commences following the expiration of the hold period.

In some aspects, the aforementioned method further comprises thefollowing steps. A step of monitoring additional occupancy data producedby the occupancy sensors for at least part of the duration of the firstgrace period, and making a third determination as to whether or not thedesignated zone remained in the unoccupied state for the entirety of thefirst grace period. And another step, wherein, based on the result ofthe third determination, the one or more luminaires, (a) fades back to aprevious higher level of illumination produced prior to the commencementof the first grace period, or (b) completes their transition to thefirst lower level of illumination. In various other aspects, theaforementioned method further comprises the following steps. A next stepof monitoring additional occupancy data produced by the occupancysensors for at least part of the duration of a prolong period, andmaking a fourth determination as to whether or not the designated zoneremained in the unoccupied state for the entirety of the prolong period.And a further step, wherein, based on the result of the fourthdetermination, the one or more luminaires, (a) fades back to a previoushigher level of illumination produced prior to the commencement of theprolong period, or (b) fades to a level of illumination associated witha switched-off state over a second grace period that commences followingthe prolong period.

Some embodiments disclose a method for managing environmental conditionswithin a physical structure comprising a plurality of linkedcommissioned units and one or more illumination sensors. The methodcomprises a first step of the one or more illumination sensorsindicating a change in illumination in a work zone. A second stepinvolves at least one of the plurality of commissioned units associatedwith the work zone and communicatively connected to the one or moresensors, receiving the indication of the change in illumination, andmaking a first determination as to whether or not an amount of changeassociated with the indication of change in illumination is greater thana preset amount. In a further third step, based on the firstdetermination, the at least one of the plurality of commissioned unitsaccesses the output of the one or more illumination sensors, and makes asecond determination as to whether or not a level of illumination in thework zone is at or above a preset level of illumination. In a fourthstep, at least one luminaire within the work zone transitions to (a)providing a predetermined minimum level of illumination over a firstfade period if the second determination indicates the level ofillumination in the work zone as being at or above the preset level ofillumination, or (b) providing a predetermined maximum level ofillumination over a second fade period if the second determinationindicates the level of illumination in the work zone as being below thepreset level of illumination.

Other embodiments may include a non-transitory computer readable storagemedium storing instructions executable by a processor to perform amethod such as one or more of the methods described herein. Yet otherembodiments may include a system including a memory and one or moreprocessors operable to execute instructions, stored in the memory, toperform a method such as one or more of the methods described herein.

In one aspect, a method comprises: operating a luminaire controller fora luminaire by executing first operating software having a firstsoftware image; receiving at the luminaire controller a second softwareimage of second operating software for the luminaire controller; theluminaire controller communicating the first software image of the firstoperating software to a first device connected to the luminairecontroller via a communication network; installing the second operatingsoftware at the luminaire controller; performing a self test of theluminaire controller. If/when the luminaire controller fails the selftest: the luminaire controller requests via the network that the firstdevice transfer the first software image to the luminaire controller viathe network, the luminaire controller receives the first software image,and the luminaire controller installs the first operating software andreverts to operation with the first operating software.

In another aspect, a lighting system comprises: a first luminaire; afirst luminaire controller which is configured to control operations ofthe first luminaire; at least one device including at least one memorystoring at least a first software image for first operating softwarewhich was previously employed by the first luminaire controller andfurther storing a first configuration data set according to which thefirst luminaire controller was previously configured; a communicationnetwork connecting the first luminaire controller and the at least onedevice to be in communication with each other, wherein the firstluminaire controller includes at least one memory storing secondoperating software, different from the first operating software, whichis employed by the first luminaire controller, and a secondconfiguration data set, different from the first configuration data set,according to which the first luminaire controller is configured.

In yet another aspect, a device comprises: a processor; a communicationinterface configured for connection to a lighting network and configuredto communicate with a plurality of luminaire controllers via thelighting network, wherein the luminaire controllers are configured tocontrol operations of a plurality of luminaires; and a memory configuredto store therein at least one of: a plurality of sets of configurationdata sets according to which various ones of the plurality of luminairecontrollers were previously configured, and a plurality of softwareimages for operating software according to which the various ones of theplurality of luminaire controllers previously operated.

As used herein for purposes of the present disclosure, the term “LED”should be understood to include any electroluminescent diode or othertype of carrier injection/junction-based system that is capable ofgenerating radiation in response to an electric signal and/or acting asa photodiode. Thus, the term LED includes, but is not limited to,various semiconductor-based structures that emit light in response tocurrent, light emitting polymers, organic light emitting diodes (OLEDs),electroluminescent strips, and the like. In particular, the term LEDrefers to light emitting diodes of all types (including semi-conductorand organic light emitting diodes) that may be configured to generateradiation in one or more of the infrared spectrum, ultraviolet spectrum,and various portions of the visible spectrum (generally includingradiation wavelengths from approximately 400 nanometers to approximately700 nanometers). Some examples of LEDs include, but are not limited to,various types of infrared LEDs, ultraviolet LEDs, red LEDs, blue LEDs,green LEDs, yellow LEDs, amber LEDs, orange LEDs, and white LEDs(discussed further below). It also should be appreciated that LEDs maybe configured and/or controlled to generate radiation having variousbandwidths (e.g., full widths at half maximum, or FWHM) for a givenspectrum (e.g., narrow bandwidth, broad bandwidth), and a variety ofdominant wavelengths within a given general color categorization.

For example, one implementation of an LED configured to generateessentially white light (e.g., a white LED) may include a number of dieswhich respectively emit different spectra of electroluminescence that,in combination, mix to form essentially white light. In anotherimplementation, a white light LED may be associated with a phosphormaterial that converts electroluminescence having a first spectrum to adifferent second spectrum. In one example of this implementation,electroluminescence having a relatively short wavelength and narrowbandwidth spectrum “pumps” the phosphor material, which in turn radiateslonger wavelength radiation having a somewhat broader spectrum.

It should also be understood that the term LED does not limit thephysical and/or electrical package type of an LED. For example, asdiscussed above, an LED may refer to a single light emitting devicehaving multiple dies that are configured to respectively emit differentspectra of radiation (e.g., that may or may not be individuallycontrollable). Also, an LED may be associated with a phosphor that isconsidered as an integral part of the LED (e.g., some types of whiteLEDs). In general, the term LED may refer to packaged LEDs, non-packagedLEDs, surface mount LEDs, chip-on-board LEDs, T-package mount LEDs,radial package LEDs, power package LEDs, LEDs including some type ofencasement and/or optical element (e.g., a diffusing lens), etc.

The term “light source” should be understood to refer to any one or moreof a variety of radiation sources, including, but not limited to,LED-based sources (including one or more LEDs as defined above). A givenlight source may be configured to generate electromagnetic radiationwithin the visible spectrum, outside the visible spectrum, or acombination of both. Hence, the terms “light” and “radiation” are usedinterchangeably herein. Additionally, a light source may include as anintegral component one or more filters (e.g., color filters), lenses, orother optical components. Also, it should be understood that lightsources may be configured for a variety of applications, including, butnot limited to, indication, display, and/or illumination. An“illumination source” is a light source that is particularly configuredto generate radiation having a sufficient intensity to effectivelyilluminate an interior or exterior space. In this context, “sufficientintensity” refers to sufficient radiant power in the visible spectrumgenerated in the space or environment (the unit “lumens” often isemployed to represent the total light output from a light source in alldirections, in terms of radiant power or “luminous flux”) to provideambient illumination (i.e., light that may be perceived indirectly andthat may be, for example, reflected off of one or more of a variety ofintervening surfaces before being perceived in whole or in part).

The term “spectrum” should be understood to refer to any one or morefrequencies (or wavelengths) of radiation produced by one or more lightsources. Accordingly, the term “spectrum” refers to frequencies (orwavelengths) not only in the visible range, but also frequencies (orwavelengths) in the infrared, ultraviolet, and other areas of theoverall electromagnetic spectrum. Also, a given spectrum may have arelatively narrow bandwidth (e.g., a FWHM having essentially fewfrequency or wavelength components) or a relatively wide bandwidth(several frequency or wavelength components having various relativestrengths). It should also be appreciated that a given spectrum may bethe result of a mixing of two or more other spectra (e.g., mixingradiation respectively emitted from multiple light sources).

For purposes of this disclosure, the term “color” is usedinterchangeably with the term “spectrum.” However, the term “color”generally is used to refer primarily to a property of radiation that isperceivable by an observer (although this usage is not intended to limitthe scope of this term). Accordingly, the terms “different colors”implicitly refer to multiple spectra having different wavelengthcomponents and/or bandwidths. It also should be appreciated that theterm “color” may be used in connection with both white and non-whitelight.

The terms “lighting fixture” and “luminaire” are used interchangeablyherein to refer to an implementation or arrangement of one or morelighting units in a particular form factor, assembly, or package. Theterm “lighting unit” is used herein to refer to an apparatus includingone or more light sources of same or different types. A given lightingunit may have any one of a variety of mounting arrangements for thelight source(s), enclosure/housing arrangements and shapes, and/orelectrical and mechanical connection configurations. Additionally, agiven lighting unit optionally may be associated with (e.g., include, becoupled to and/or packaged together with) various other components(e.g., control circuitry) relating to the operation of the lightsource(s). An “LED-based lighting unit” refers to a lighting unit thatincludes one or more LED-based light sources as discussed above, aloneor in combination with other non LED-based light sources. A“multi-channel” lighting unit refers to an LED-based or non LED-basedlighting unit that includes at least two light sources configured torespectively generate different spectrums of radiation, wherein eachdifferent source spectrum may be referred to as a “channel” of themulti-channel lighting unit.

The term “controller” is used herein generally to describe variousapparatus relating to the operation of one or more light sources. Acontroller can be implemented in numerous ways (e.g., such as withdedicated hardware) to perform various functions discussed herein. A“processor” is one example of a controller which employs one or moremicroprocessors that may be programmed using software (e.g., microcode)to perform various functions discussed herein. A controller may beimplemented with or without employing a processor, and also may beimplemented as a combination of dedicated hardware to perform somefunctions and a processor (e.g., one or more programmed microprocessorsand associated circuitry) to perform other functions. Examples ofcontroller components that may be employed in various embodiments of thepresent disclosure include, but are not limited to, conventionalmicroprocessors, application specific integrated circuits (ASICs), andfield-programmable gate arrays (FPGAs).

In various implementations, a processor or controller may be associatedwith one or more storage media (generically referred to herein as“memory,” e.g., volatile and non-volatile computer memory such as RAM,PROM, EPROM, and EEPROM, floppy disks, compact disks, optical disks,magnetic tape, etc.). In some implementations, the storage media may beencoded with one or more programs that, when executed on one or moreprocessors and/or controllers, perform at least some of the functionsdiscussed herein. Various storage media may be fixed within a processoror controller or may be transportable, such that the one or moreprograms stored thereon can be loaded into a processor or controller soas to implement various aspects of the present invention discussedherein. The terms “program” or “computer program” are used herein in ageneric sense to refer to any type of computer code (e.g., software ormicrocode) that can be employed to program one or more processors orcontrollers.

In one network implementation, one or more devices coupled to a networkmay serve as a controller for one or more other devices coupled to thenetwork (e.g., in a master/slave relationship). In anotherimplementation, a networked environment may include one or morededicated controllers that are configured to control one or more of thedevices coupled to the network. Generally, multiple devices coupled tothe network each may have access to data that is present on thecommunications medium or media; however, a given device may be“addressable” in that it is configured to selectively exchange data with(i.e., receive data from and/or transmit data to) the network, based,for example, on one or more particular identifiers (e.g., “addresses”)assigned to it.

The term “network” as used herein refers to any interconnection of twoor more devices (including controllers or processors) that facilitatesthe transport of information (e.g. for device control, data storage,data exchange, etc.) between any two or more devices and/or amongmultiple devices coupled to the network. As should be readilyappreciated, various implementations of networks suitable forinterconnecting multiple devices may include any of a variety of networktopologies and employ any of a variety of communication protocols.Additionally, in various networks according to the present disclosure,any one connection between two devices may represent a dedicatedconnection between the two systems, or alternatively a non-dedicatedconnection. In addition to carrying information intended for the twodevices, such a non-dedicated connection may carry information notnecessarily intended for either of the two devices (e.g., an opennetwork connection). Furthermore, it should be readily appreciated thatvarious networks of devices as discussed herein may employ one or morewireless, wire/cable, and/or fiber optic links to facilitate informationtransport throughout the network.

The term “user” as user herein refers to any entity, human orartificial, that interacts with systems and methods described herein.For example, the term includes, without limitation, occupants of a spacesuch as an office worker or visitor, remote users of a space, a facilitymanager, a commissioning engineer, a building IT manager, a serviceengineer, and an installer.

It should be appreciated that all combinations of the foregoing conceptsand additional concepts discussed in greater detail below (provided suchconcepts are not mutually inconsistent) are contemplated as being partof the inventive subject matter disclosed herein. In particular, allcombinations of claimed subject matter appearing at the end of thisdisclosure are contemplated as being part of the inventive subjectmatter disclosed herein. It should also be appreciated that terminologyexplicitly employed herein that also may appear in any disclosureincorporated by reference should be accorded a meaning most consistentwith the particular concepts disclosed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings, like reference characters generally refer to the sameparts throughout the different views. Also, the drawings are notnecessarily to scale, emphasis instead generally being placed uponillustrating the principles of the invention.

FIG. 1A illustrates a block diagram of an embodiment of a system formanaging environmental conditions within a physical structure, theembodiment comprising several modules, two IP luminaires and anenvironment control device.

FIG. 1B illustrates a block diagram of an embodiment of a system formanaging environmental conditions within a physical structure, theembodiment comprising several modules, two IP luminaires, an environmentcontrol device and an IR remote control device.

FIG. 1C illustrates components of IP luminaires and the interfaceslinking the components in accordance with some embodiments.

FIG. 1D illustrates a block diagram of an embodiment of a system formanaging environmental conditions within a physical structure, theembodiment comprising an environment manager module, a sensor, a memoryand a commissioned unit.

FIG. 2A illustrates the component architecture of a lighting network inaccordance with some embodiments.

FIG. 2B illustrates a block diagram of an embodiment of a system formanaging environmental conditions within a physical structure, and thedifferent network environments associated with various components of thesystem.

FIG. 3A illustrates an embodiment of a stand-alone, connectedconfiguration of a system for managing environmental conditions.

FIG. 3B illustrates an embodiment of an end-to-end integratedconfiguration of a system for managing environmental conditions.

FIG. 4A illustrates a block diagram of components of an embodiment of anenvironment manager module, along with other devices and components withwhich the environment manager module is communicatively connected.

FIG. 4B illustrates a block diagram of various selected components of anISPF cloud-deployed embodiment of a system for managing environmentalconditions within a physical structure.

FIG. 5 illustrates a block diagram of a commissioning and configurationprocess utilized by components of a system for managing environmentalconditions, in accordance with some embodiments.

FIG. 6 illustrates a commissioned unit such as an open-plan roomcomprising multiple device groups in accordance with one embodiment.

FIG. 7 illustrates a commissioned unit such as an open-plan room, asystem user in the open-plan room, several zones surrounding the user,and devices that lie within and outside of these zones.

FIG. 8 illustrates an occupancy-based control method for responding tothe detection of occupancy in a previously unoccupied space, performedby some embodiments of a system for managing environmental conditions.

FIG. 9A illustrates an occupancy-based control method for responding tothe detection of a lack of occupancy in a previously occupied space,performed by some embodiments of a system for managing environmentalconditions.

FIG. 9B illustrates an occupancy-based control method for responding tothe detection of occupancy in a previously unoccupied space, performedby some embodiments of a system for managing environmental conditions.

FIG. 10 illustrates another occupancy-based control method forresponding to the detection of a lack of occupancy in a previouslyoccupied space, performed by some embodiments of a system for managingenvironmental conditions.

FIG. 11 illustrates an occupancy-based control method for responding tothe detection of a lack of occupancy in a previously occupied space,performed by some embodiments of a system for managing environmentalconditions, the method incorporating the use of a hold period, a graceperiod, and a prolong period for confirming occupancy status.

FIG. 12 illustrates an occupancy-based control method for responding tothe detection of occupancy in a previously unoccupied cell zone,performed by some embodiments of a system for managing environmentalconditions.

FIG. 13 illustrates an occupancy-based control method for responding tothe detection of a change in occupancy in a corridor zone, performed bysome embodiments of a system for managing environmental conditions.

FIG. 14 illustrates an occupancy-based control method for responding tothe detection of a change in occupancy in a meeting zone, performed bysome embodiments of a system for managing environmental conditions.

FIG. 15 illustrates a method for responding to a request for a differentenvironmental scene in a meeting zone, performed by some embodiments ofa system for managing environmental conditions.

FIG. 16 illustrates a daylight-based control method for responding to adetected change in illumination in a work zone, performed by someembodiments of a system for managing environmental conditions.

FIG. 17 illustrates a daylight-based control method for responding to adetected change in natural illumination in a space, performed by someembodiments of a system for managing environmental conditions.

FIG. 18 illustrates an interactive digital floor plan depicting thelocation of commissioned units, in accordance with some embodiments of asystem for managing environmental conditions.

FIG. 19 illustrates a method for determining the power-up behavior of acommissioned or uncommissioned unit, performed by some embodiments of asystem for managing environmental conditions.

FIG. 20 illustrates a method for handling a control request, performedby some embodiments of a system for managing environmental conditions.

FIG. 21 illustrates a method for handling a manually-activated personalcontrol request, performed by some embodiments of a system for managingenvironmental conditions.

FIG. 22 illustrates an arrangement of commissioned units and associatedPoE switches for reducing the visual impact of PoE switch failure, inaccordance with some embodiments of a system for managing environmentalconditions.

FIG. 23 illustrates a method for self-diagnosis and recovery performedby commissioned units in some embodiments of a system for managingenvironmental conditions.

FIG. 24 illustrates an embodiment of an interactive graphical userinterface displayed as a front end to an environment manager module, inaccordance with some embodiments of a system for managing environmentalconditions.

FIG. 25 illustrates an embodiment of an interactive graphical userinterface displayed as a front end to a commissioning module, inaccordance with some embodiments of a system for managing environmentalconditions.

FIG. 26 illustrates an embodiment of an interactive area wizard for useas part of a front end to a commissioning module, the area wizardpermitting a user to specify various parameters that together define thefunction(s) of an area within a physical structure.

FIG. 27 illustrates an embodiment of an interactive graphical userinterface for use in commissioning a new device for use in a system formanaging environmental conditions.

FIG. 28 illustrates an example embodiment of an illumination systemincluding a luminaire controller connected on a network to devices whichare configured to store software images and configuration data set forrestore points.

FIG. 29 illustrates another example embodiment of an illumination systemincluding two luminaire controllers which are each connected on anetwork to devices which are configured to store software images andconfiguration data set for restore points.

FIG. 30 illustrates another example embodiment of an illumination systemincluding three luminaire controllers which are each connected on anetwork to devices which are configured to store software images andconfiguration data set for restore points.

FIG. 31 illustrates an example embodiment of an illumination systemduring a normal operating mode.

FIG. 32 illustrates an example embodiment of an illumination systemduring an operating software upgrade where a luminaire controller hasreceived a new software image.

FIG. 33 illustrates an example embodiment of an illumination systemwhere a luminaire controller which has received a new software imagestores its current software image and configuration data set to agateway controller.

FIG. 34 illustrates an example embodiment of an illumination systemwhere a luminaire controller which has received a new software imagefails a self test after installing an operating software update.

FIG. 35 illustrates an example embodiment of an illumination systemwhere a luminaire controller has reverted to its previous software imageand configuration data set after a failed operating software upgrade.

FIG. 36 illustrates a flowchart of an example embodiment of a method ofautonomously creating a restore point for a luminaire and autonomouslyrestoring the luminaire to a working state when it malfunctions after anoperating software upgrade.

DETAILED DESCRIPTION

Reference is now made in detail to illustrative embodiments of theinvention, examples of which are shown in the accompanying drawings.

In the following detailed description, for purposes of explanation andnot limitation, representative embodiments disclosing specific detailsare set forth in order to provide a thorough understanding of thepresent teachings. However, it will be apparent to one having ordinaryskill in the art having had the benefit of the present disclosure thatother embodiments according to the present teachings that depart fromthe specific details disclosed herein remain within the scope of theappended claims. Moreover, descriptions of well-known systems,apparatuses and methods may be omitted so as to not obscure thedescription of the representative embodiments. Such systems, methods andapparatuses are clearly within the scope of the present teachings.

FIG. 1A illustrates a system 100A for managing environmental conditionswithin a physical structure. The system includes an environment managermodule 110, a commissioning module 120, a gateway module 130, IPluminaires 140 and 150 and an environment control device 160. Otherembodiments of system 100A may include additional or fewer environmentalmanager modules, IP luminaires, commissioning modules, gateway modulesand/or environment control devices. The components of system 100A arecommunicatively linked using links L1 through L9, as depicted in FIG. 1.The term “physical structure” as used herein refers to any buildingstructure, whether or not freestanding, permanent, enclosed, or covered.This term includes for example, office, residential, recreational,educational, governmental, and commercial buildings and complexes, aswell as parking lots and garages. The term “link” as used herein refersto any connection or component that enables the communication ofinformation between at least two system components. For example, a linkincludes a wired or wireless communications connection, a radiofrequency communications connection, and an optical communicationsconnection. A link may also indicate a shared communication protocol,software or hardware interface, or remote method invocations orprocedure calls.

Environment manager module 110 may be implemented in hardware, anycombination of hardware and computer code (e.g. software or microcode),or entirely in computer code. This module may be executed on one ormultiple processors.

In some embodiments, manager module 110 may provide an InteractiveSystem Productivity Facility (ISPF) based central monitoring andmanagement dashboard. Manager module 110 may also provide interactiveuser interfaces for various features such as the visualization ofcurrent lighting or other environmental statuses in system 100A,visualization of occupancy information at various levels of granularity,visualization of energy consumption information at various levels ofgranularity, visualization of alarms. Additionally, manager module 110may receive personal control commands (e.g. related to light level andtemperature) from smart phone applications and translate such commandsinto lighting control or HVAC control commands, manage system-widelighting control, and manage scheduling of tasks. Environment managermodule 110 may also participate in software upgrades (also known asupdates), manage monitoring data such as data related to energyconsumption and occupancy, and manage alarms and other system healthdiagnostic data. FIG. 4A illustrates various components of an embodimentof an environment manager module, and the description of FIG. 4Aprovides further details on this module. Additional details onfunctional and other aspects of environment manager modules such as theenvironment manager module 110 may be found throughout thespecification.

As depicted in FIG. 1A, environment manager module 110 is able toreceive information from environment control device 160 via link L2. L2may be a personal control interface for a smart phone. Manager module110 is also able to communicate with commissioning module 120 via linkL1. L1 may facilitate the communication of commissioning module projectfiles. In some embodiments, L1 may also represent an XML database withextensions for xCLIP compatible luminaires. Lastly, manager module 110is also able to communicate with gateway module 130 via link L3. L3represents, according to some embodiments, the EnvisionIP interface.

Commissioning module 120 may be implemented in hardware, any combinationof hardware and computer code (e.g. software or microcode), or entirelyin computer code. This module may be executed on one or multipleprocessors. In many embodiments of system 100A, commissioning module 120is used to commission devices such as IP luminaires, switches andsensors. Commissioning module 120 may also be used to prepare a floorplan for a space, discover and associate devices with system 100A,localize devices by, for example, coded light detection techniques. Itmay also be used for pre-commissioning system 100A and the devicesassociated with it. For example, commissioning module 120 may be usedfor creating groups of devices and allocating spaces within a structurefor specific purposes. In many embodiments of system 100A, commissioningmodule 120 may be used to commission devices such as IP luminaires, andcontrol devices, by, for example, localizing devices in accordance withprepared floor plans, programming lighting scenes, configuring deviceand control parameters, and calibrating sensors. Commissioning module120 may also be used to for performing software upgrades. Otherfunctionality associated with commissioning module 120 may be foundthroughout the specification, and particularly in the descriptionassociated with FIG. 5.

As depicted in FIG. 1A, commissioning module 120 is able to communicatewith environment manager module 110 via link L1, gateway module 130 vialink L4, with IP luminaire 150 via link L6. L1 has been described abovein connection with the description of environment manager module 110. Inmany embodiments, L4 may represent an EnvisionIP or xCLIP interface, andL6 may represent an EnvisionIP interface.

Gateway module 130 may be implemented in hardware, any combination ofhardware and computer code (e.g. software or microcode), or entirely incomputer code. This module may be executed on one or multipleprocessors. In some embodiments, a hardware implementation of gatewaymodule 130 may involve an STM32 chip. Gateway module 130 may beassociated with a particular floor of a physical structure, and may sendand/or receive data from multiple devices such as IP luminaires locatedon that floor. In some embodiments, gateway module 130 may send and/orreceive data from more than 1000 devices such as IP luminaires, sensorsand HVAC devices.

Gateway module 130 is configured to provide a variety of functions. Forexample, it may provide a gateway between an EnvisionIP interface foruse in commissioning luminaires and the RS-485 standard, as well asprovide services for translating various application and networkprotocols. In many embodiments, it may also facilitate the routing ofdata between multiple gateway modules within system 100A, andparticipate in system diagnostics and/or hardware roll calls duringwhich the gateway module 130 may determine whether or not devices underits control are still online. Gateway module 130 may also be responsiblefor caching and/or reporting offline devices to the environment managermodule 110. Gateway module 130 may also be responsible for localscheduling tasks and the management of monitoring and diagnostic data.For example, gateway module 130 may monitor one or more areas within aphysical structure for energy consumption and occupancy, and diagnoseand report system health information on the area level. It may alsostore area monitoring information. In some embodiments, gateway module130 monitors all DyNet and EnvisionIP traffic in a part of the system.It may store and/or cache this information, and forward it to theenvironment manager module 110 so that the environment manager modulehas an exact overview of the state of all the commissioned devices atany given time. With respect to scheduling, time critical events may beforwarded by gateway module 130 to the environment manager module 110immediately, while events that are not time critical may be locallycached and uploaded to the manager module 110 in batches. In cases wherethe manager module 110 cannot be reached, all events may be locallycached and uploaded to the manager module 110 when it becomes reachableagain. Gateway module 130 may also interface with an HVAC systemassociated with system 100A, and discover new devices. In manyembodiments, multiple gateway modules such as gateway module 130 may becommunicatively linked with a single environment manager module 110,where each gateway module 130 acts as a floor controller for aparticular floor of a building. In many embodiments, gateway module 130may also: log and store all or a subset of received environment controlcommands; log and report all events and state changes within the systemback to the environment manager module 110, send commands coming fromthe commissioned units that this gateway module 130 controls and/ormonitors to another gateway module that controls and/or monitors anotherpart of the system (common area send responsibility); send commandscoming from another gateway module that controls and/or monitors anotherpart of the system to the commissioned units that this gateway module130 controls and/or monitors (common area receive responsibility);(transparently) bridge between EnvisionIP networks and DyNet RS485networks, allowing the system to be extended, for example, with allexisting DyNet (RS485) products; actively monitor, log and store theavailability of all commissioned units and devices, and report anychange in their availability to the environment manager module 110.

As depicted in FIG. 1A, gateway module 130 is able to exchangeinformation with IP luminaires 140 and 150 via link L5, and withenvironment manager module 110 via link L3, and commissioning module 120via link L4. L3 and L4 were previously described in connection withmanager module 110 and commissioning module 120 respectively. In manyembodiments, L5 may represent an EnvisionIP or an xCLIP interface.

IP luminaire 140 is associated with sensor 140-1, light source 140-2,and control module 140-3. In some embodiments, sensor 140-1 and lightsource 140-2 are located within the same device or housing. In someembodiments, control module 140-3 comprises computer code (e.g. softwareor microcode) executing on one or more processors housed within the samedevice or housing as sensor 140-1 and/or light source 140-2. Lightsource 140-2 may be capable of performing one or more light actuatingfunctions, such as turning on/off, dimming, and tunable white light orcolored light production. Sensor 140-1 is a sensor capable of sensing,for example, one or more of daylight, occupancy, IR, carbon dioxide,humidity and temperature. Control module 140-3 provides one or morecontrol functions for controlling the behavior of other modules anddevices, such as one or more of light source 140-2, sensor 140-1,commissioning module 120, environment manager module 110, gateway module130, and IP luminaire 150.

IP luminaire 140 may provide one or more external interfaces forcommunicating with other modules of system 100A. For example, IPluminaire 140 may provide an EnvisionIP interface (e.g. links L5 and L7)for use in commissioning light source 140-2 and/or for use by controlmodule 140-3 to influence the behavior of other area luminaires andsensors communicatively connected to itself (e.g. light source 150-2 andsensor 150-1), light source 140-2, or sensor 140-1. IP luminaire 140 mayalso provide an xCLIP interface for use by control module 140-3 toaccess and control basic capabilities of light source 140-2 or otherlight sources communicatively connected to IP luminaire 140. The xCLIPinterface may also be used by other system modules (e.g. gateway module130) for accessing sensor data generated by sensors accessible to IPluminaire 140 (e.g. sensors 140-1 and 150-1), and energy consumption anddiagnostic data available to light source 140-2 and/or IP luminaire 140.FIG. 1C and its associated description provide further details regardingthe components of an IP luminaire and the various interfaces used bythese components.

Environment control device 160 may be any device for controllingenvironmental conditions in a space. Such devices include, withoutlimitation, smart phones such as the iPhone®, tablet or handheldcomputing devices such as the iPad®, laptop computers, touch sensitiveand/or voice activated input and/or display devices communicativelyconnected to one or more processors, and desktop computing devices.

In some embodiments, the components of system 100A depicted in FIG. 1Amay interact in the following way. Environment control device 160receives a user's input indicating his/her desire to change anenvironment condition in his or her vicinity. For example, controldevice 160 may be a smart phone, and the user may indicate, using agraphical user interface displayed on the smart phone, his/her desire toincrease the level or intensity of light in a work zone, such as a tabletop in the room where the user is physically present. The graphical userinterface may also be used to control other lighting parameters, such ascolor, color temperature and direction. Meanwhile, IP luminaires 140 and150, which control illumination in the aforementioned work zone, eachgenerate coded light signals comprising codes identifying, for example,themselves and/or light sources 140-2 and 150-2 respectively. IPluminaire 150 transmits the coded light signal comprising the codeidentifying itself and/or light source 150-2 to environment controldevice 160 via link L8 and IP luminaire 140 transmits the coded lightsignal comprising the code identifying itself or light source 140-2 vialink L9. Via link L2, environment control device 160 transmits one ormore signals comprising an environment control request. The environmentcontrol request contains information regarding changes the user of theenvironment control device 160 wishes to make in his or her environment,as well as information on the devices, such as IP luminaires, which maybe used to carry out the user's wishes. For example, the environmentcontrol request may encode the user's desire to increase the level oflight in a work zone such as a table top, as well as identificationinformation from the coded light signals received by environment controldevice 160. The environment manager module 110, executing on one or moreprocessors, receives the one or more signals comprising the environmentcontrol request from the environment control device 160, and generatesan environment control command In many embodiments, the environmentcontrol command comprises the information encoded in the environmentcontrol request, but in a format understandable by the gateway module orcommissioned units (e.g. IP luminaire) to which it is transmitted.Furthermore, while the environment control request may contain moregeneral information regarding desired environmental changes in aparticular room or work zone, the environment control command is morespecific with regard to the implementation of the requested changesencoded in the environment control request. For example, the environmentcontrol command may contain specific instructions that, when processedby a group of IP luminaires, cause the IP luminaires to effect specificchanges in illumination. Environment manager module 110 thereafter maytransmit, via link L3, the environment control command to gateway module130. Gateway module 130 may store data associated with the environmentcontrol command, such as identification information associated with theIP luminaire(s) that will respond to the user's desired change inlighting level. Gateway module 130 may then communicate via link L5 toinstruct IP luminaire 150 and/or IP luminaire 140 to adjust theirillumination to produce the light level requested by the user.

FIG. 1B illustrates a system 100B for managing environmental conditionswithin a physical structure. The system includes an environment managermodule 110, a commissioning module 120, an IR remote control 130, IPluminaires 140 and 150, and an environment control device 160. IPluminaire 140 is associated with sensor 140-1, light source 140-2, andcontrol module 140-3, and IP luminaire 150 is associated with sensor150-1, light source 150-2 and control module 150-3. Some otherembodiments of system 100B may include additional or fewer environmentalmanager modules, IP luminaires, commissioning modules, environmentcontrol devices and/or IR remote controls. The components of system 100Bare communicatively linked using links L1 through L7, as depicted inFIG. 1B. Identically named components of systems 100A and 100B may beidentical in their makeup and behavior. However, environment managermodule 110 and IP luminaires 140 and 150 may behave differently in thealtered configuration of system 100B. Additionally, links L1 and L2 ofsystem 100B are the same as links L1 and L2 of system 100A; links L5,L6, and L7 of system 100B are the same as links L8, L7, and L9,respectively, of system 100A.

IR remote control 130 is any device that uses infrared light to issuecommands to receiver devices. IR remote control 130 may use link L8 toissue control commands to IP luminaire 140 or its components, such assensor 140-1 and light source 140-2. In many embodiments of system 100B,link L8 may represent the RC-5 protocol.

In some embodiments, the components depicted in FIG. 1B may interact inthe following way. Environment control device 160 receives a user'sinput indicating his/her desire to change an environment condition inhis or her vicinity. For example, control device 160 may be a smartphone, and the user may indicate, using a graphical user interfacedisplayed on the smart phone, his/her desire to increase the level oflight in a work zone, such as a table top in a room where the user isnot physically present. Meanwhile, IP luminaires 140 and 150, whichcontrol illumination in the aforementioned work zone, each generatecoded light signals comprising codes identifying luminaires 140-2 and150-2 respectively. IP luminaire 140 transmits the coded light signalcomprising the code identifying light source 140-2 to environmentcontrol device 160 via link L7, and IP luminaire 150 transmits the codedlight signal comprising the code identifying light source 150-2 toenvironment control device 160 via link L5. Via link L2, environmentcontrol device 160 transmits one or more signals comprising anenvironment control request. The environment manager module 110,executing on one or more processors, receives the one or more signalscomprising the environment control request from the environment controldevice 160, and generates an environment control command. Details on theenvironment control request and environment control command werespecified previously in the context of FIG. 1A. Environment managermodule 110 may thereafter transmit, via link L3, the environment controlcommand to IP luminaire 140 and/or IP luminaire 150 to adjust theillumination produced by light source 140-2 and/or light source 150-2 inorder to achieve the level of illumination requested by the user ofenvironment control device 150. The same or a different user may alsouse IR remote control 130 while located proximally to IP luminaire 140,to directly issue a command to IP luminaire 140 in order to adjust theillumination produced by light source 140-2.

FIG. 1C illustrates components of IP luminaires 110C and 120C and theinterfaces linking the components in accordance with some embodiments.IP luminaire 110C comprises components control module 110C-1, DC-DC LEDdriver 110C-2, ILB sensor 110C-3, and one or more LEDs 110C-4. Likewise,IP luminaire 120C comprises components control module 120C-1, DC-DC LEDdriver 120C-2, ILB sensor 120C-3, and one or more LEDs 120C-4. Controlmodules 110C-1 and 120C-1 may be any type of control module described inthe context of FIG. 1A. In some embodiments control modules 110C-1and/or 120C-1 may be STM32 based PoE devices. Control Modules 110C-1 and120C-1 are shown to encode data for transmission to DC-DC LED drivers110C-2 and 120C-2, respectively, using pulse width modulation (PWM).

In LEDs, as voltage increases, current tends to increase rapidly.Accordingly, even small fluctuations in voltage tends to cause largefluctuations in current, which in turn causes damage to LEDs. Due to therisk of damage to LEDs owing to such voltage fluctuations, LED driversare used to connect LEDs to a voltage source such as a mains power or abattery. LED drivers control input power to the LEDs, so that they maybe safely operated. LED drivers 110C-2 and 120C-2 are electroniccircuits which convert input power into a current source in whichcurrent is constant despite voltage fluctuations. Control modules 110C-1and 120C-1 may communicate with other system modules over xCLIPinterfaces, and with each other over the EnvisionIP interface. ILBsensors 110C-3 and 120C-3 receive control signals from IR remotecontrols 140C-1 and 140C-2, respectively, over RC5 interfaces. PoEswitch 130C receives data over EtherNet/IP interfaces, and transmits thereceived data as well as electrical power to IP luminaire 110C via PoEand EtherNet/IP interfaces.

FIG. 1D illustrates a system 100D for managing environmental conditionswithin a physical structure. The system comprises an environment managermodule 110, at last one commissioned unit 120D, at least one memory130D, and at least one sensor 140D. Environment manager module 110 iscommunicatively connected to commissioned unit 120D via link L3, and tomemory 130D via link LK. Commissioned unit 120D is communicativelyconnected to sensor 140D and memory 130D via link LK. LK is anyconnection or component that enables the communication of informationbetween at least two system components. For example, a LK includes awired or wireless communications connection, a radio frequencycommunications connection, and an optical communications connection. LKmay also indicate a shared communication protocol, software or hardwareinterface, or remote method invocations or procedure calls.

Commissioned unit 120D may comprise one or more devices that areassociated with each other within a system such as system 100A or 100D,and that behave according to particular configurations of internaltriggers (triggers arising from within the commissioned unit) andexternal triggers (triggers arising outside the commissioned unit).Triggers may include, for example, sensor data, or a manual or centralcontrol. A single device may be part of multiple commissioned units.Commissioned units such as commissioned unit 120D may also behierarchically organized. For example, a commissioned unit may compriseother commissioned units, and may influence the behavior of thesecommissioned units. In some embodiments, sensor 140D is a sensor in adesignated zone within the physical structure. Sensor 140D is configuredto produce data indicative of, for example, motion, occupancy, sound,the presence of one or more gases, illumination, humidity, andtemperature. In such embodiments, commissioned unit 120D, which iscommunicatively connected to sensor 140D through link LK and toenvironment manager module 110 through link L3, is configured to receivethe data produced by sensor 140D. Commissioned unit 120D may also beconfigured to determine whether or not the sensor data represents astatus change associated with the designated zone. In many embodiments,commissioned unit 120D is also configured to update, through link LK, atleast a memory 130D, in accordance with the sensor data representing thestatus change.

FIG. 2A depicts the component architecture 200A of a lighting network inaccordance with some embodiments. In the illustrated architecture, thereare three main component layers: a core layer, a distribution layer, andan edge layer, each surrounded by dotted lines. The core layer comprisesan environment manager module 210A that is communicatively connected toa left wing router and a right wing router. The routers may have flashcard backup capabilities and may be configured such that they each hasaccess to one IP subnet per port. Environment manager module 210A isdirectly or indirectly communicatively connected to: various componentsin the lighting network of a system for managing environmentalconditions (e.g. left wing router, right wing router and floor switchesin the distribution layer), and to the IT network of the structure whoseenvironment the environment manager module 210A is managing. In manyembodiments, the environment manager module 210A may gain access toHVAC-related data through the structure's IT network.

The distribution layer may consist of one IP switch per floor of thestructure, and per core layer router (depicted as Switch Floor 1 (Left),Switch Floor 1 (Right), Switch Floor 2 (Left), Switch Floor 2 (Right) .. . Switch Floor N (Left), Switch Floor N (Right)). In many embodiments,these IP switches support the spanning tree protocol. The edge layerconsists of a number of rings (depicted as a single curved arrow throughside edge layers) per distribution layer switch, and a gateway moduleper floor for providing floor-level lighting control. Each ring consistsof a number of PoE switches, daisy chained and connected to two ports ofthe respective distribution layer switch in a ring. Such an arrangementprovides the advantage that if a ring of PoE switches is broken at anypoint in the ring configuration, all of the PoE switches may still bereached over the network.

FIG. 2B illustrates a block diagram of an embodiment 200B of a systemfor managing environmental conditions within a physical structure, andthe different network environments associated with various components ofthe system. Embodiment 200B comprises an environment manager module, acommissioning module, and multiple gateway modules that may be any typeof environment manager module, commissioning module, and gateway module,respectively, described in the context of FIG. 1A. The multiple gatewaymodules are depicted as being communicatively linked to multiplecommissioned units (e.g. luminaires and sensors). In this embodiment,facility users may use hand held devices such as smart phones executingpersonal control applications (apps) to send requests for environmentalchanges to the environment manager module via the depicted communicationlink. The smart phones executing the personal control apps are shown tobe operational within the Internet but not within the IT network or thelighting network associated with the system for managing environmentalconditions. Additionally, facility managers may utilize browser-basedapplications (also connected to the Internet) such as a centraldashboard or other environmental management application to send similarrequests for environmental changes to the environment manager module viathe Internet. The personal control apps and the browser basedapplications may also receive information (e.g. data on energy consumedby luminaires within the lighting network) from the environment managermodule for display on their user interfaces. In the depicted embodiment,the environment manager module, the commissioning module and theirshared one or more databases are within the physical structure's privateIT network. The multiple gateway modules and commissioned units are,however, within the structure's private lighting network. Data leavingor entering the private networks via the environment manager module maybe required to pass through firewalls.

FIG. 3A illustrates an embodiment 300A of a stand-alone, connectedconfiguration of a system for managing environmental conditions.Embodiment 300A includes router 310A, area controller 320A, PoE powersupplies 330A and 340A, and two clusters of luminaires 350A-1 through350A-4 and 360A-1 through 360A-4. In the configuration of embodiment300A, the IP infrastructure need not be connected to the Internet.

Router 310 is any networking device that forwards data packets in acomputer network. It is connected to PoE power supplies 330 and 340 andarea controller 320 via link L1, which provides an xCLIP interface foraccessing data from the depicted clusters of luminaires as well assensor, energy consumption and diagnostics data available from theluminaires. Power over Ethernet or PoE refers to any systems(standardized or ad-hoc) for providing electrical power and data onEthernet cabling. PoE allows a single cable to provide both a dataconnection and electrical power to devices such as wireless accesspoints, IP Phones, IP luminaires or IP cameras. Although other standardssuch as USB can provide power to devices over data cables, PoE allowsfor far longer cable lengths. In PoE systems, data and power may becarried on the same conductors, or on dedicated conductors on a singlecable. PoE therefore eliminates the need for power supplies at theEthernet/IP device.

Area controller 320 may be implemented in hardware, any combination ofhardware and computer code (e.g. software or microcode), or entirely incomputer code executing on one or more processors. Area controller 320may be used to perform various area control functions for a defined area(e.g. a floor of a building). In many embodiments, area controller 320provides an interactive graphical user interface for system users tomanage the control functions. Other such control functionality may beadditionally or alternatively be performed by devices such as luminairesor IP luminaires with which area controller 320 interacts. According tosome embodiments, area controller 320 may, for example: (a) controlmultiple commissioned units or zones within a building; (b) be used togroup devices and/or commissioned units during the commissioningprocess; (c) determine area occupancy and adjust lighting for an areaaccordingly; (d) adjust background light levels or regulate lightinglevels based on changes in available natural light for a group ofcommissioned units; (e) collect and analyze sensor and/or energyconsumption data from one or more luminaires and sensors; and (f)participate in scheduling environmental changes such as changes inlighting levels within an area. Software downloads may also occurthrough the area controller. In many embodiments, the area controllermay play an intermediate role, where it fetches a software download froma central server, and distributes the upgrade to respective luminairesand other devices appropriately. Area controller 320 may also act as asecurity bridge between the luminaire clusters operating within aprivate lighting network, and a third party private network such as anetwork comprising a building management system (BMS). In someembodiments, area controller 320 operates within a private IP network,and software tools such as a maintenance tool being executed on anauthorized system user's hand held device may exchange data with areacontroller 320 by temporarily connecting to the IP network.

Luminaires 350-1 through 350-4, and 360-1 through 360-4 may be IPluminaires such as IP luminaire 140 or luminaires comprising lightsources such as light source 140-2, described in the context of FIG. 1A.Luminaire networks in embodiment 300A may be compliant with IPstandards, and may be able to operate in an IP network. The luminairesare each connected to PoE power supply 330 through either link L2 or L3.Link L2 may provide a PoE interface, an xCLIP interface or an IPinterface for communications between PoE Power Supply 330 and theluminaires.

FIG. 3B depicts an embodiment 300B of an end-to-end integratedconfiguration of a system for managing environmental conditions.Embodiment 300B includes router 310, area controller 320, PoE powersupplies 330 and 340, two clusters of luminaires 350-1 through 350-4 and360-1 through 360-4, lighting controller dashboard 370, buildingcontroller dashboard 380, floor controller 390, HVAC controller 395,HVAC active airflow controller 395-1 and temperature controller 395-2.Many of the components of embodiment 300B may be similar or identical toidentically-named components of embodiment 300A. For example, router310, area controller 320, PoE power supplies 330 and 340, and luminaires350-1 through 350-4 and 360-1 through 360-4 may be, respectively, anytype of router, area controller, PoE power supply and luminaire devicedescribed with respect to embodiment 300A of FIG. 3A.

Lighting controller dashboard 370 may be, for example, computer codedisplaying a user interface that is a part of, or executing on one ormore processors communicatively connected to, system modules such asenvironment manager module 110 of FIG. 1. The user interface of lightingcontroller dashboard may be displayed on any environment control devicediscussed in the context of FIG. 1, such as environment control device160. For example, lighting controller dashboard 370 may be anapplication executing on a handheld device such as an iPhone® or iPad®.Dashboard 370 is communicatively connected to area controller 320,router 310 and PoE power supplies 330 and 340 through links L1 and L5,which may provide an xCLIP or IP interface for the exchange of data.Lighting controller dashboard 370 may also be used for monitoringpurposes (e.g. monitoring energy consumption and system health), and fordeployment of lighting schedules. Dashboard 470 may also collect andaggregate information, such as energy consumption, system health, andoccupancy information, from multiple area controllers to provide itsusers a complete and current view of the functioning system.

Building controller dashboard 380, floor controller 390, and HVACcontroller 395 may be implemented in hardware, any combination ofhardware and computer code (e.g. software or microcode), or entirely incomputer code executing on one or more processors. These components ofembodiment 300B may be used to perform various functions related to themanagement of a building's HVAC system, such as monitoring and controlof a building's temperature and air flow. In many embodiments, buildingcontroller dashboard 380 may display a user interface that is a part of,or executing on one or more processors communicatively connected to,system modules such as environment manager module 110 of FIG. 1. Theuser interface of the building controller dashboard 380 may be displayedon any environment control device discussed in the context of FIG. 1,such as environment control device 160. For example, building controllerdashboard 380 may be an application executing on a handheld device suchas an iPhone® or iPad®. There may be multiple floor controllers thatprovide dashboard 380 information regarding environmental conditions ondifferent floors of a building, which the dashboard may then display onits user interface.

In the configuration of embodiment 300B, the lighting subsystem (e.g.luminaire clusters, PoE power supplies, area controller and router) maybe communicatively connected to a 3^(rd) party IP networkinfrastructure, which may also be connected to the Internet. In theseembodiments, the building controller dashboard 380, floor controller390, HVAC controller 395, HVAC active airflow controller 395-1 andtemperature controller 395-2 may be integral components of a 3^(rd)party building management system operating within the 3^(rd) party IPnetwork infrastructure. The 3^(rd) party IP network may share buildinginformation such as HVAC information with the lighting subsystem and thelighting controller dashboard 370 when necessary. For example, thelighting controller dashboard 370 may display HVAC information such astemperature in particular areas close to commissioned units with largenumbers of luminaires. This temperature information may be obtained bythe lighting controller dashboard 370 via a connection to the 3^(rd)party IP network infrastructure.

FIG. 4A illustrates a block diagram of the components of an embodimentof an environment manager module, along with other devices andcomponents with which the environment manager module is communicativelyconnected. The architecture of the environment manager module may bebased on the n-tier enterprise server-client architectural model, inwhich functions such as application processing, application datamanagement, and presentation are physically and/or logically separated.

The front end of the environment manager module may be a web-basedapplication that executes on top of an Indoor Service PresentationFramework (ISPF). In FIG. 4A, the front end of the environment managermodule may be displayed on the device (e.g. laptop computing device)indicated by the monitor icon and located next to the icon depicting afacility manager. ISPF is a software framework that enables the creationof web-based applications for lighting control, status monitoring, andenergy management for HVAC and lighting management systems. It is acloud-based and enterprise-wide software solution that is capable ofinterfacing with controllers in a system for managing environmentalconditions such as system 100 of FIG. 1. An environment manager moduleweb-based application that interfaces with the end user (e.g. facilitymanager) provides, in many embodiments, an application frame, a portalapplication, a login module and help functionality. The ISPF framework,on top of which the environment manager module executes, provides theenvironment manager module with the information necessary to provide theapplication frame and portal application, as described in further detailbelow. The presentation layer of the environment manager module depictedin FIG. 4A is based on the Model-View-Controller (MVC) design paradigm.A layer is a common logical structuring mechanism for various elementsthat constitute a software solution. The presentation layer mainlyconsists of standard portlets such as a control portlet, a schedulerportlet, a macro portlet, a user settings portlet, and a notificationsportlet. Portlets are pluggable software user interface (UI) componentsthat are displayable in a web portal. A portlet also typically comprisesa set of JavaScript objects. They produce fragments of markup code (e.g.HTML, XHTML, WML), which are then aggregated into a complete UI for theweb portal. In many embodiments, a web portal may comprise a pluralityof non-overlapping portlet windows. In such embodiments, each portletwindow may display the UI component(s) of a specific portlet. Thepresentation layer may be implemented, for example, using Liferay®portal server, DOJO®, MxGraph®, JqChart® and JavaScript®.

In many embodiments, the presentation layer invokes the service layerusing the REST/SOAP interface, as the ISPF exposes available services asREST and SOAP interfaces. These services typically utilize the businessobjects defined in the business layer to realize their functionality.The service layer may also expose the REST APIs in XML and JSON format,as input and output. Client web applications may interact with theenvironment manager application executing as a server by invoking theREST/SOAP interface over HTTP/HTTPS using XML/JSON.

The business layer manages business objects that interface with one ormore database servers and controllers, in its associated system formanaging environmental conditions, via the data access layer andcommunication gateway. In many embodiments, business objects aremodularized such that multiple services associated with the servicelayer may invoke the same business object to realize its exposedfunctionality. In many embodiments, one service may use multiplebusiness layer objects to realize its functionality. The business layermay also invoke the message bus for communicating with controllers inits associated system for managing environmental conditions.

The data access layer provides a way to reduce the degree of couplingbetween business logic and persistence logic. Application business logicoften requires domain objects which are persisted in a database. Thedata access layer allows for the encapsulation of code to performcreate, read, update and delete (CRUD) operations against persistencedata without affecting the rest of the application layers (e.g. thepresentation layer). This means that any change in the persistence logicwill not adversely affect any other layers of the environment managermodule. The data access layer therefore enables applications such as anenvironment manager module web-based application to seamlessly integratewith a new database provider.

The mediation engine provides rule-based routing of data within theenvironment manager module. In some embodiments, the mediation enginemay comprise a Java® object-based implementation of enterpriseintegration patterns that uses an API to configure routing and mediationrules. For example, the rule-based routing of the mediation engine mayensure that all alarm events encountered by the environment managermodule are routed to a database for persisting, and all network eventsare persisted in another database.

The message bus provides queuing functionality and is used forprocessing all communications from controllers that are received by theenvironment manager module. Particularly, the message bus providesqueuing functionality for the prioritizing of information received fromthe business layer and from the communication gateway. For example, allinformation (e.g. requests) received by the communication gateway (e.g.from commissioned units) are routed through the message bus using themediation engine. Any responses to such requests from the communicationgateway are routed through the message bus. In many embodiments, themessage bus may be used, for example, for: (a) prioritizing andforwarding communication gateway requests received from the businesslayer, notification emails and SMS messages; (b) pushing status andalarm messages to the presentation layer for display on a UI; (c)executing asynchronous processes; (d) synchronous and asynchronousmessaging; and (d) dispatching messages in serial and in parallel tomultiple modules.

In many embodiments, the message bus comprises a synchronization managercomponent, used for publishing real time updates from controllers andcommissioned devices to front end applications. Applications (e.g. acentral dashboard presenting information processed by the environmentmanager module) may subscribe to real time updates from controllers(e.g. alarms, lighting events, energy updates). Whenever a real-timeupdate is received, for example, by the communication gateway, thesynchronization manager may notify all subscribers.

The NoSQL database (an in-memory database) is used for storing the mostrecent 24 hours of trend data. In many embodiments, all the data in thein-memory database shall be stored in a cache and shall not bepersisted. In many embodiments, this database is executed in a separateprocess as compared to the environment manager module itself, and thedatabase may be accessed using SQL.

The database server is used to store control, management and monitoringdata. The database server may be local or remote to the environmentmanager module. If local, the database server may be created duringproduct installation. A remote database may be a new or existingdatabase that may be customer-managed. The database server may accessmultiple schemas to manage the variety of information it stores. Forexample, an OpenFire® schema may contain XMPP server related tables.These tables may contain information related to users, rooms, andpermissions. A liferay® schema may contain tables for managing portals,portlets, users, and UI personalization data. An alarm schema maycomprise tables for schedule and alarm management.

Communication gateway provides a means for the environment managermodule to communicate with devices and commissioned units. In variousembodiments, the communication gateway subscribes to device events usingCOM Java® wrapper classes it uses to communicate with a Field ServiceLayer (FSL) accessible to the devices and commissioned units (FSL notshown in FIG. 4A). When events such as lighting events are registered bycommissioned units, the communication gateway is notified of the eventby the FSL. The communication gateway thereafter transmits the eventinformation as appropriate to the upper layers (e.g. message bus,business layer, services layer, presentation layer). The communicationgateway communicates with the upper layers of the environment managermodule in two ways: (1) through REST services accessible only by thebusiness layer components, and (2) using the message bus (e.g. using theXMPP protocol for all requests and responses). Both these mechanisms areconfigurable. When the environment manager module has been deployed on acloud such that the communication gateway is hosted on a privatenetwork, the message bus communication option may be enabled.

In many embodiments, to transmit data to the upper layers from the FSL,the communication gateway converts FSL objects received from the FSLlayer to an ISPF common object model. To transmit data from the upperlayers of the environment manager module to the FSL (which is how thecommunication gateway interfaces with commissioned units), thecommunication gateway converts ISPF common object model objects to FSLobjects. In some embodiments, the communication gateway uses the ComfyJlibrary to communicate with the FSL. The ComfyJ library provides the JNIwrapper classes for the FSL COM objects. In such embodiments, thecommunication gateway may be executed in a separate JVM process, forwhich a minimum of 2 GB of heap space may be allocated.

In many embodiments, the communication gateway comprises a communicationgateway API, code for converting domain specific objects to the ISPcommon object model, and ComfyJ generated wrapper classes (e.g. ComfyJgenerated wrapper classes of the FSL for control and monitoringpurposes). The communication gateway API is typically used for sendingand receiving messages from the message bus.

ISPF ETL (Extract Transform and Load) is used to extract data from theNoSQL Audit Schema and transform the data into a star data model forloading into the trend schema of the database server. In manyembodiments, ETL is a separate process in ISPF which runs in a separateexecution context. The ETL process also runs on a scheduled basis, whichis configurable. A default schedule may be to execute the ETL processonce every 12 hours.

The analytics layer analyzes data produced by commissioned units andproduces textual and graphical reports for display on front endapplications. The analytics layer may utilize a report design orpublishing toolset to control the look and feel of the reports generatedand may also use an analysis toolset (e.g. Pentagon Mondrian) for dataanalysis. The analytics layer may also provide an online analyticalprocessing (OLAP) solution where data such as lighting network log datais collected into a central repository and analyzed for use by multipleend user applications.

FIG. 4B illustrates a block diagram of various selected components of anISPF cloud-deployed embodiment of a system for managing environmentalconditions within a physical structure. The cloud deployment comprises acloud machine 405C executing an environment overlord server 410C and itsrelated modules (message bus 430C, mediation engine 435C, analyticengine 415C, cache server 420C and database server 425C). These relatedmodules may be similar to similarly named modules in FIG. 4A. In thecloud deployment of FIG. 4B, however, multiple environment managermodules (e.g. 410-1C and 410-2C) are deployed within separate privatenetworks (e.g. 405-1C and 402-2C). These multiple envision managermodules may exchange data with the cloud machine 405C through theirrespective message buses as indicated. Connections between the overlordserver 410C and the environment manager modules 410-1C and 410-2C may besecured over a TLS protocol.

In the embodiment depicted in FIG. 4B, the environment overlord server410C, analytic engine 415C, cache server 420C, database 425C, messagebus 430C and mediation engine 435C are all execution environmentsexecuting on the cloud machine, which is a hardware device. The analyticengine 415C may comprise a Pentaho Mondrian® engine, the cache server420C may be an EhCache® server, the database 425C may be an MS. SQL®database server, and the mediation engine 435C may be an Apache® Camelengine. Gateway modules 445-1C and 445-2C may be any type of gatewaymodules described in the context of FIG. 1A. The overlord server 410 mayutilize or otherwise incorporate technologies such as Liferay® v6.1, JRE1.6, Apache CXF, DOJO v1.8, MXGraph, Spring 3, Strophe, JQChart,JasperReports, True License, InstallAnyWhere, and/or JPivot.

Commissioning

As initially discussed above in the context of FIG. 1A, commissioningmodule 120 participates in a commissioning process performed, forexample, by system 100A for managing environmental conditions within aphysical structure. According to some embodiments, the commissioningprocess comprises the steps depicted in FIG. 5. In various otherembodiments, the steps in the process need not be performed in the ordershown, one or more steps may be omitted, and one or more steps notdepicted may be added to the process shown in FIG. 5. The steps includestep 500, in which one or more devices are localized; step 510, duringwhich commissioned units are created; step 520, in which commissionedunits are bound to devices (e.g. sensors) or other commissioned units;step 530, in which commissioned units are linked; step 540, in whichcommissioned units are configured for use within a system such as system100A; and step 550, in which commissioned units are programmed asnecessary.

In step 500 of FIG. 5, devices to be associated with a system such assystem 100A are localized. Localization is the mapping of devices suchas luminaires, sensors and controllers to a physical location within aphysical structure such as a building. Physical structures such asbuildings are generally associated with a hierarchy. For example, acampus may comprise multiple buildings, a building may comprise multiplefloors, and a floor may comprise multiple rooms. During step 500, adevice such as a sensor may be localized by being associated with aparticular corner or a room within a building. Additionally, devices aswell as spaces within structures may be associated with functions duringthe localization process. For example, a room may be assigned thefunction of a cell-office, a corridor, a restroom, a meeting room, or anopen-plan office. A device may be assigned the function of, for example,occupancy sensing, light sensing, light production or control. Duringthe commissioning process, a digital floor-plan of a structure, such asa building, may also be created. According to some embodiments, thefloor plan may comprise all the details regarding the hierarchy of thestructure (e.g. floors, functional spaces within floors, devices andtheir locations within the functional spaces). A floor plan may alsocontain information on functional links between control devices andcommissioned units. The floor plan may be interactively created by anauthorized user accessing a commissioning tool executed by one or moreprocessors associated with the commissioning module 120, wherein thecommissioning tool visually illustrates the various levels of hierarchyassociated with the structure. An exemplary digital floor plan isdepicted in FIG. 18. The floor plan may also visually identify alllocalized devices and their properties.

Localization may also involve devices such as luminaires or commissionedunits comprising luminaires being triggered to flash and visuallyidentify their location. Localization may also be accomplished usingcoded light technology. Generally, coded light technology involves anon-visible modulation of light to contain information about the lightsource, such as a unique identifier and location information. Examplesof devices that may be localized using coded light technology includes,without limitation, area controllers, gateway modules, luminaires, ILBsensors, PoE sensors, PoE manual control user interfaces, and PoEswitches. During and/or following the localization process, devices mayreport their properties to a commissioning tool associated, for example,with commissioning module 120 of FIG. 1A. A luminaire may report, forexample, information indicative of its type (e.g. CCT, max output),available sensors, hardware version, software version and a unique ID.As a result of the localization step of 500, the digital floor map maygraphically reflect the various localized devices at their appropriatelocations, along with their properties (e.g. type, unique ID).

In step 510, commissioned units are created. A commissioned unitcomprises one or more devices that are associated with each other withina system such as system 100A, and that behave according to particularconfigurations of internal triggers (triggers arising from within thecommissioned unit) and external triggers (triggers arising outside thecommissioned unit). Triggers may include, for example, sensor data, or amanual or central control. A device may be part of multiple commissionedunits. And commissioned units may be used to define a hierarchy within aphysical structure such as a building. For example, a commissioned unitmay be (1) a group of devices such as luminaires and sensors, (2) one ormore individual devices, or (3) a combination of one or morecommissioned units and individual devices. A commissioned unit may alsobe an area (e.g. a work space, room, corridor) comprising one or moregroups of devices such as luminaires, sensors, and controllers.

In many embodiments, a commissioned unit may be assigned one or moretemplates. Templates are a collection of predefined system settings ordevice parameter configurations designed to adjust the behavior of oneor more devices so as to produce a set of environmental conditions. Asystem for managing environmental conditions, such as system 100A,operating within a large space may need to create different lighting andother environmental conditions in different parts of the space that facedifferent circumstances (e.g. high foot traffic, low occupancy).Templates provide an efficient mechanism for capturing the preferredbehavior of devices in these different spaces under commonly occurringcircumstances. Templates may specify, for example, minimum light levelsin a corridor of an office building during work hours.

In some embodiments, commissioning of units in step 510 may berule-based. In rule-based commissioning, multiple devices may becommissioned as a single commissioned unit based on predefined rules. Insome such embodiments, the rule may indicate the size of thecommissioned unit in terms of the number of devices that may be includedas part of the unit. Moreover, other dynamic parameters such as theposition of a system user in an area, and the dimensions and mountingpositions of the devices around the user, a temporary or permanentcommissioned unit may be formed. FIG. 7 depicts an embodiment ofrule-based commissioning, where the central dark spot represents asystem user. In this embodiment, devices that are at least partiallylocated within the first circular area surrounding the user (the taskarea 710) may form one commissioned unit, and devices primarily locatedin the outer circular area that lies outside the first circular areasurrounding the user (immediate surrounding area 720) may form anothercommissioned unit. Each commissioned unit may be controlled separately,and lighting rules may apply differently to the same device, dependingupon which commissioned unit it is associated with.

In other embodiments, commissioning of units in step 510 may be fixed.In fixed commissioning, pre-commissioned units or groups are created forexample, by logically dividing a zone such as an open-plan office intodedicated zones (e.g. task zones, corridors, decorative zones), andcreating one or more commissioned units comprising devices that arelocalized to these dedicated zones. FIG. 6 depicts several commissionedunits (e.g. Task Groups A, B, and C; Decorative Group A; and CorridorGroup A) formed based on the logical division of an open plan room intodedicated zones (three task zones, a decorative zone, and a corridorzone), and on the location and spatial configuration of luminaireswithin each dedicated zone. The creation of commissioned units of step510 may also involve the addition of devices (e.g. luminaires, controlsand sensors) to previously commissioned units, and linking newlycommissioned units to existing commissioned units. Linking is discussedbelow in the context of step 530.

Grouping multiple devices into a single commissioned unit allows forefficient management of environmental conditions. For example, multipleIP luminaires and their associated sensors may be responsible forilluminating a particular task zone such as a table top. Rather thanseparately issuing commands to each IP luminaire in the commissionedunit or separately monitoring sensor data for each of the differentsensors, systems such as system 100A may issue one command for eachcommissioned unit when necessary to adjust an environmental conditionsuch as illumination, which may be applied after any necessaryprocessing to all the lighting units within the commissioned unit.Similarly, sensor data from multiple sensors within the commissionedunit may be reported in the aggregate to system 100A modules such as theenvironment manager module 110, rather that repeatedly reporting sensordata from each individual sensor.

In step 520, commissioned units comprising lighting or HVAC devices arebound to control and sensor devices or commissioned units comprisingsuch devices. The commissioning tool described previously will, in manyembodiments, allow an authorized user (e.g. a commissioning engineer) toselect sensors (e.g. occupancy sensors, light sensors) for associationwith commissioned units. Binding commissioned units to particularsensors or types of sensors allows for the creation of commissionedunits that are suitable for participating in occupancy-based ordaylight-based environmental control. These control mechanisms aredescribed in the context of FIGS. 8-17 below.

In many embodiments of the process depicted in FIG. 5, an authorizeduser (e.g. commissioning engineer) may bind multiple occupancy sensorsto the same commissioned unit. In such an arrangement, the commissionedunit, when under occupancy-based control, may be directed to displayoccupied behavior if just one of the bound sensors senses occupancy, andmay be directed to display unoccupied behavior only if all of its boundsensors fail to sense occupancy. The user may also bind multipledaylight sensors to the same commissioned unit. In such a configuration,the aforementioned commissioning tool may also enable the authorizeduser to configure how multiple light-related events arising from themultiple daylight sensors are aggregated and/or processed. Thecommissioning tool may, in various embodiments, allow an authorized userto bind manual and personal controllers (both fixed and mobile) tocommissioned units. This allows for the creation ofmanually-controllable commissioned units, and allows for the assignmentof a scope of control for each controller device. This in turn resultsin the efficient management of control requests received from thevarious controllers in a building, and an overall increase in theefficient management of environmental conditions within the building.

In step 530, commissioned units are linked. Linking commissioned unitsgenerally requires associating the commissioned units in a memory. Oncelinked, a commissioned unit may affect the behavior of the othercommissioned units with which it is linked. For example, whether or nota first commissioned unit switches off its lights when the onlyremaining occupant of the area leaves, may depend upon whether or notanother linked commissioned unit providing illumination in an adjacentarea is switched off. In many embodiments, if a first commissioned unitcomprising luminaires is linked to a second commissioned unit comprisingluminaires, and the first unit detects occupancy, the light produced bythe second unit may transition to a preconfigured interlinked lightlevel in response to the detected occupancy. Linking commissioned units,therefore, allows the system to appropriately control environmentalconditions in larger spaces (e.g. large open office spaces) bycoordinating the response of multiple commissioned units scoped tovarious areas within these spaces when changes (e.g. changes inoccupancy) are detected in just one area.

Under some circumstances, coordinating the behavior of multiplecommissioned units may be necessary to provide a comfortable environmentfor occupants of a large open space within a building. For example, whenfew occupants are remaining in cell offices within an open-plan officespace, it will be energy efficient to turn off lighting in unoccupiedareas of the office space. At the same time, it may be beneficial toensure that illumination in areas adjacent to the occupied cell officesas well as some common corridor areas is maintained in order to avoid asense of isolation for the remaining occupants of the open-plan officespace.

In step 530, the commissioning tool may also allow an authorized user tolink commissioned units to one or more HVAC grids or areas. In manyembodiments, a single HVAC area or grid may comprise multiple lightinggroups. In such embodiments, sensors associated with the multiplelighting groups may be associated with an HVAC area identifier for thesingle HVAC area or grid. When such a configuration is operational,sensor information from commissioned units within the multiple lightinggroups may be forwarded to HVAC area controllers associated with thesingle HVAC area or grid.

Step 540 is a configuration step, during which various configurableparameters of commissioned units are specified using, for example, thecommissioning tool. Such parameters may control a commissioned unit'sdefault behavior under various conditions. During the configurationstep, templates may be assigned to or disassociated from commissionedunits, a commissioned unit's power-up behavior may be specified, controloptions may be enabled and disabled, timing parameters (e.g. fade time,dwell time, hold time, grace fade time, smart time) may be specified,occupancy-related parameters (e.g. maximum light level when occupied,minimum light level when occupied) may be specified, general lightingparameters (e.g. background light level, task light level) may bespecified, user control parameters (e.g. dim step, dim speed, retentiontime) may be specified, and priority levels associated with differentcontrol options (e.g. occupancy-based control, daylight-based control,manual control, personal control, and central control) may be set.During this step, the commissioning tool associated with, for example,the commissioning module 120 of system 100A, or the central dashboardassociated with, for example, with the environment manager module 110 ofsystem 100A, may selectively disallow a user (e.g. a facility manager)from specifying and/or adjusting certain parameters for commissioneddevices or units that are likely to be outside of the user's level ofcompetency. During this step, an authorized user may also be able toassociate an application behavior template with any commissioned unit.An application behavior template is a collection of parameter or otherconfiguration values suitable for a particular application.

To make the commissioning process more efficient, the commissioning tooland/or the central dashboard also permits the simultaneous configuringof multiple commissioned units. For example, a user may elect to havetwo or more commissioned units receive the same configuration settingsas previously selected for another commissioned unit. The user may alsouse the commissioning tool to copy and paste configuration settings fromone device or commissioned unit to another. In various embodiments, thecommissioning tool or central dashboard may also be used to revertconfigured parameters of any device or commissioned unit to previoussettings such as factory default settings. Moreover, the commissioningtool may be used to remove links to sensors and controls. Thecommissioning tool may also enable an authorized user to manually orautomatically calibrate sensors (e.g. daylight sensors). While a sensoris calibrating, it may not be able to communicate with the rest of thesystem. A calibrated sensor may provide visual or other feedback oncecalibrated successfully.

Step 550 is a programming step, during which the user may create andassign a template to one or more commissioned units such that thecommissioned units are able to behave in accordance with the template ifrequired. For example, the user may use the commissioning tool to createa template of a particular lighting scene for a commissioned unit byspecifying lighting parameters for various luminaires included withinthe commissioned unit. Such a lighting scene may thereafter be used as adefault scene in a meeting zone associated with the commissioned unit,when the meeting zone transitions from an unoccupied to an occupiedstate. In some embodiments, the commissioning tool may allow the user tosave current light settings of a commissioned unit as a new scene. Acommissioned unit may have multiple associated scenes for applicationunder different circumstances, such as under specific occupancyconditions, daylight conditions, and/or at specific times of the day.

Remote Re-Commissioning

In some embodiments, the central dashboard may allow an authorized userto remotely re-commission previously commissioned units. In order toperform the re-commissioning, the central dashboard may provide userinterface means for searching for and locating the units to bere-commissioned on a displayed digital floor plan of the physicalstructure in which the device is housed. Users may be able to search forthe commissioned units using the unit's type, location within thestructure, identification number or other information. Commissionedunits matching the user's search criteria may thereafter be displayedand selectable by the user. Once a commissioned unit or device isselected or otherwise identified for remote re-commissioning, the usermay be allowed to view and edit various parameters associated with theunit or device. The central dashboard may also allow the user todisassociate the unit or device for one commissioned unit andre-associate the device or unit with a different device or unit.

Managing Environmental Conditions—Automatic Controls

According to many embodiments, environmental conditions within astructure such as a building are monitored and managed to provideoccupants optimal conditions (e.g. lighting, temperature, airflow),while at the same time conserving energy. This section focuses onoccupancy and daylight-based control of environmental conditions. Whilemany of the embodiments described below rely on pre-programmed logic andsystem parameters, other embodiments function by monitoring conditionssuch as light levels and temperature in real time, receiving feedbackand/or instructions from occupants or remote users of the spaces, andadjusting environmental conditions accordingly.

Occupancy-Based Control

Occupancy-based control of environmental conditions occurs automaticallyin reaction to changes in occupancy within a space. Occupancy-basedcontrol mechanisms may, however, in many embodiments apply inconjunction with manual, central, or personal control mechanisms. In thesections below, details regarding configurable parameters referred to inthe descriptions of each figure below appear prior to the figuredescriptions themselves.

Configurable Parameters: MaxWhenOccupied and MinWhenOccupied

Using the commissioning tool, an authorized user such as a commissioningengineer may configure parameters indicative of maximum and minimumlight output by a commissioned unit associated with an occupied space.In some embodiments, the parameters indicative of the maximum light thatshould be output when an associated area is occupied (MaxWhenOccupied)and the minimum light that should be output when the associated area isoccupied (MinWhenOccupied) may each be set to a percentage value between0% and 100% of output ability. However, the parameter MaxWhenOccupiedmay not, in some embodiments using Coded Light technology, be set to avalue above 90%. Likewise, in some embodiments using Coded Lighttechnology, the parameter MinWhenOccupied may not be set to a valuebelow 25%. These restrictions may be required in some embodiments toaccount for requirements of Coded Light technology and/or physicallimitations of luminaires.

Configurable Parameters: Light Level 1 and Light Level 2

Light Level 1 and Light Level 2 are configurable parameters associatedwith occupancy-based control of environmental conditions. In manyembodiments, Light Level 1 signifies the light level for providing alower background-level of illumination, and Light Level 2 signifies thelight level for providing a higher task-level of illumination. A defaultvalue for the Light Level 1 parameter may be 300 lux, while a defaultvalue for the Light Level 2 parameter may be 500 lux. An authorized usermay be able to use a tool such as the commissioning tool, the centraldashboard or other manual or personal controllers to set and/or alterthese parameters. In various embodiments, these parameters may trackvalues associated with MinWhenOccupied to MaxWhenOccupied.

FIG. 8 illustrates an occupancy-based control method 800 for respondingto the detection of occupancy in a previously unoccupied space,performed by some embodiments of a system for managing environmentalconditions. It comprises steps 810-840. Method 800 may be performed, forexample, by components of a system 100A or 100B depicted in FIGS. 1A and1B respectively. In step 810, sensor input is received. The sensor inputmay be from one or multiple sensors and the sensor(s) may be any type ofoccupancy sensor such as a motion sensor. The sensor input may bereceived for processing by the sensor itself, or by one or more modulesdepicted in FIG. 1A or 1B (e.g. environment manager module 110, gatewaymodule 120, or IP luminaire 150). In step 820, the sensor input isprocessed, and a determination is made that a designated zone hastransitioned from an unoccupied state (e.g. without any occupants) to anoccupied state (e.g. with at least one occupant). In step 830, inresponse to the determination made in step 820, at least one luminairetransitions from not providing illumination to providing apre-configured background-level of illumination (e.g. Light Level 1)within a pre-configured reaction time period. In some embodiments, theluminaire that is more closely associated with a sensor sensing thechange in occupancy status (e.g. the luminaire housing the sensor orotherwise physically proximate to the sensor) transitions first to thebackground-level of illumination. The at least one luminaire may be partof a single commissioned units or multiple commissioned units that arescoped to or otherwise associated with the designated zone.

In step 840, a plurality of luminaires associated with the designatedzone produce a swarm lighting effect. A swarm lighting effect isproduced when a plurality of luminaires each switches to a higher levelof light, but the time at which each luminaire performs the transitionoccurs in accordance with its distance from a first luminaire performingthe transition. Luminaires that are closer to the first luminaireperform the transition to a higher light level earlier than luminairesthat are further away from the first luminaire. This creates the effectof light “spreading” throughout a space from a particular originatingpoint. In some embodiments, the swarm effect, once started, may takeplace without further coordination from system modules such asenvironment manager module 110 or gateway module 130. For example, an IPluminaire such as IP luminaire 140 may not only cause its own lightsource (e.g. light source 140-2) to switch to producing a higher levelof light, but may also communicate with another IP luminaire locatedproximally but further away from the first luminaire (e.g. IP luminaire150) via, for example, its control module (e.g. control module 140-3)and link L7 such that IP luminaire 150 then switches its own lightsource (e.g. light source 150-2) to produce a higher level of light. Inother embodiments, other system modules, such as environment managermodule 110 or gateway module 130 may coordinate the swarm effect by, forexample, selectively instructing luminaires or to turn on or produce ahigher level of light.

Configurable Parameter: Interlinked Light Level

Interlinked Light Level is a configurable parameter associated withoccupancy-based control of environmental conditions. In manyembodiments, it signifies the level of light produced by a commissionedunit when occupancy is detected not by the commissioned unit itself butby one or more linked commissioned units. In many embodiments, theInterlinked Light Level parameter ranges from 0% to 100% of aluminaire's output, and may be configured at a 1% granularity. Thecommissioning tool may be used to configure the Interlinked Light Levelfor any commissioned unit, and the central dashboard or a manual orpersonal controller may be used to reset this parameter for one or morecommissioned units.

FIG. 9A illustrates an occupancy-based control method 900 for respondingto the detection of a lack of occupancy in a previously occupied space,performed by some embodiments of a system for managing environmentalconditions. It comprises steps 910A-940A. Method 900A may be performed,for example, by components of a system 100A or 100B depicted in FIGS. 1Aand 1B respectively. The method of FIG. 9A may be used to communicateoccupancy information between linked commissioned units, which in turnmay be used to achieve energy savings.

In step 910A, sensor input is received. The sensor input may be from oneor multiple sensors and the sensor(s) may be any type of occupancysensor such as a motion sensor. The sensor input may be received forprocessing by the sensor itself, or by one or more modules depicted inFIG. 1A or 1B (e.g. environment manager module 110 or gateway module120). In step 920A, the sensor input is processed, and a determinationis made that a designated zone has transitioned from an occupied state(e.g. with at least one occupant) to an unoccupied state (e.g. with nooccupants). In step 930A, one or more memories accessible to luminairecontrollers or commissioned units associated with luminaire controllersin at least the designated zone are updated to reflect that thedesignated zone has transitioned to an unoccupied state. In manyembodiments, the one or more memories may also be accessible to othersystem modules such as environment manager module 110 and gateway module130.

In step 940A, a plurality of luminaires or lighting units associatedwith the designated zone is transitioned to providing illumination at anInterlinked Light Level. The association with the designated zone mayarise due to the plurality of luminaires or lighting units belonging toone or more commissioned units linked to a commissioned unit scoped tothe designated zone. In many embodiments, the plurality of luminaires orlighting units is accessible to at least one IP luminaire or at leastone commissioned unit in the designated zone. The plurality ofluminaires or lighting units may be part of the same commissioned unit,or different commissioned units that are linked during the commissioningprocess. In some embodiments, the command or instruction to transitionto an Interlinked Light Level may be propagated from one IP luminaire(e.g. IP luminaire 140 of system 100A) to another communicatively linkedIP luminaire (e.g. IP luminaire 150 of system 100A) without coordinationfrom more central system modules such as environment manager module 110or gateway module 130. In some other embodiments, environment managermodule 110 or gateway module 130 may instruct each commissioned unitlinked to a commissioned unit in the designated zone to produce anInterlinked Light Level, and each IP luminaire that is part of thecommissioned unit may thereafter cause its own luminaires to transitionto the Interlinked Light Level. In some embodiments, a secondcommissioned unit linked to a first commissioned unit scoped to thedesignated zone may switch its luminaires or lighting units to theInterlined Light Level only if the second commissioned unit is notscoped to another zone that is occupied.

FIG. 9B illustrates an occupancy-based control method 900B illustratesan occupancy-based control method for responding to the detection ofoccupancy in a previously unoccupied space, performed by someembodiments of a system for managing environmental conditions. Itcomprises steps 910B-940B. Method 900B may be performed, for example, bycomponents of a system 100A or 100B depicted in FIGS. 1A and 1Brespectively.

In step 910B, occupancy sensors produce data indicative of a designatedzone transitioning to an occupied state from an unoccupied state. Instep 920B, at least a first luminaire, associated with a first linkedcommissioned unit, produces a background level of illumination within apredetermined reaction period following the production of the sensordata. The first linked commissioned unit may be linked to a plurality ofcommissioned units, and may be components of a system for managingenvironmental conditions described herein. In step 930B, the firstlinked commissioned unit transmits data indicative of the state changeof the designated zone. In some embodiments, the data indicative of thestate change may be transmitted by the first linked commissioned unitdirectly to another commissioned unit to which it is linked, or to asystem module such as environment manager module 110 or gateway module130. The first linked commissioned unit may also transmit the data byupdating a memory accessible to other system modules or commissionedunits with the data indicative of the state change. In step 940B, asecond commissioned unit, linked to the first commissioned unit,receives the data indicative of the state change, and causes a secondluminaire or lighting unit to alter its illumination. In someembodiments, the second commissioned unit itself retrieves the dataindicative of the state change from, for example, a memory or systemmodule that the first linked commissioned unit updated with the dataindicative of the state change. The second luminaire or lighting unitmay alter its illumination, by, for example, increasing or decreasingthe light level or intensity of light it produces, changing the color orcolor temperature of the light it produces, or changing the direction ofthe light it produces. The desired alteration of its illumination may bestored on the second commissioned unit itself, or received from othersystem modules such as environment manager module 110 or gateway module130.

Configurable Parameters: Grace Fading and Fade Time

The grace fading parameter indicates whether or not a fading effecttaking place within a fade time will be performed by a commissioned unitwhen transitioning between one environmental condition (e.g. lightlevel) to another. The parameter may be enabled or disabled for anycommissioned unit that is capable of performing the fade effect. Thecommissioning tool or central dashboard may be used to configure thegrace fading and fade time parameters for any commissioned unit, and thecentral dashboard or other manual or personal controller may be used toreset the parameter for commissioned units.

FIG. 10 illustrates another occupancy-based control method 1000 forresponding to the detection of a lack of occupancy in a previouslyoccupied space, performed by some embodiments of a system for managingenvironmental conditions. It comprises steps 1010-1040. Method 1000 maybe performed by components of a system 100A or 100B depicted in FIGS. 1Aand 1B respectively. The method of FIG. 10 may be used to communicateoccupancy information between linked commissioned units so that energysavings may be achieved.

In step 1010, sensor input is received. The sensor input may be from oneor multiple sensors and the sensor(s) may be any type of occupancysensor such as a motion sensor. The sensor input may be received forprocessing by the sensor itself, or by one or more modules depicted inFIG. 1A or 1B (e.g. environment manager module 110, or gateway module120). In step 1020, the sensor input is processed, and a determinationis made that a designated zone has transitioned from an occupied state(e.g. with at least one occupant) to an unoccupied state (e.g. with nooccupants). In step 1030, one or more memories accessible to IPluminaires or commissioned units in at least the designated zone areupdated to reflect that the designated zone has transitioned to anunoccupied state. In many embodiments, the one or more memories may alsobe accessible to other system modules such as environment manager module110 and gateway module 130.

In step 1040, a plurality of luminaires or commissioned units associatedwith the designated zone is switched off in compliance with a fadeeffect. The plurality of luminaires or commissioned units may be scopedto the designated zone directly or indirectly by being linked to one ormore commissioned units that are scoped to the designated zone. Theplurality of luminaires may be part of the same commissioned unit, ordifferent commissioned units that are linked during the commissioningprocess.

The fade effect may involve gradually transitioning one or moreluminaires or lighting units to producing lower levels of light untilthe luminaires or lighting units effectively produce no illumination. Insome embodiments, a commissioned unit may only comply with the fadeeffect if a particular parameter (e.g. grace fading) is enabled for thatunit. Other details with respect to the fade effect (e.g. the amount oftime required to transition from providing the present level of light toa level of light associated with a switched off state) may be configuredper commissioned unit. Accordingly, each commissioned unit participatingin step 1040 to transition the plurality of luminaires or lighting unitsto a switched off state may perform its own version of the fade effect.In some embodiments, the command or instruction to transition toswitching off may be received from a central system module such asenvironment manager module 110 or gateway module 130 by eachcommissioned unit scoped to the designated zone. The command maythereafter be processed and propagated from one IP luminaire (e.g. IPluminaire 140 of system 100A) to another communicatively linked IPluminaire (e.g. IP luminaire 150 of system 100A) of each commissionedunit without further coordination from system modules such asenvironment manager module 110 or gateway module 130.

Configurable Parameter: Hold Period

Hold period is a configurable parameter associated with occupancy-basedcontrol of environmental conditions. In many embodiments, hold period isthe period of time needed for the system to ensure that a determinedcondition is correct or still applicable. It helps avoid situationswhere temporary changes in occupancy lead to frequent and unnecessaryadjustments to environmental conditions. For example, after sensorsinitially indicate that a zone has become vacant, and if the sensorsstill indicate vacancy after the hold period has elapsed, this implieswith a greater likelihood that the monitored zone is truly vacant andthat the vacancy is not the result of occupants temporarily steppingoutside the monitored zone. In many embodiments, the hold period mayrange from 1 to 35 minutes, with a default value of 15 minutes. Manualcontrollers may allow a user to alter the hold period with a granularityof 1 minute. The commissioning tool may be used to configure the holdperiod for any commissioned unit, and the central dashboard or othermanual or personal controller may be used to reset the hold period forone or more commissioned units.

Configurable Parameter: Grace Period

Grace period is a configurable parameter associated with occupancy-basedcontrol of environmental conditions. In many embodiments, it signifiesthe time needed for the system to ensure that a determined detectedenvironmental condition still persists after the passage of a particularperiod of time. In some embodiments, the grace period is an additionaltime period initiated after the hold period has expired, to provide anadditional duration of time during which sensor output is monitored todetermine if a detected change in occupancy is persistent for an evenlonger period of time. In many embodiments, the grace period may rangefrom 0 to 25 seconds, with a default value of 5 seconds. Manualcontrollers may allow a user to alter the grace period with agranularity of 1 second. The commissioning tool may be used to configurethe grace period for any commissioned unit, and the central dashboard orother manual or personal controllers may be used to reset the graceperiod for one or more commissioned units.

Configurable Parameter: Prolong Period

Prolong period is a configurable parameter associated withoccupancy-based control of environmental conditions. In manyembodiments, it signifies the time needed for the system to ensure thata determined detected environmental condition still persists after thepassage of a particular period of time. In some embodiments, the prolongperiod is an additional time period initiated after a first grace periodhas expired, to provide an additional duration of time during whichsensor output is monitored to determine if a detected change inoccupancy is persistent for an even longer period of time. In manyembodiments it is used as an added precautionary measure to ensure anarea's unoccupied status just prior to turning luminaires or lightingunits in the area off. Manual controllers may allow a user to manuallyalter the prolong period with a particular granularity. Thecommissioning tool may be used to configure the prolong period for anycommissioned unit, and the central dashboard or other manual or personalcontroller may be used to reset the prolong period for one or morecommissioned units.

FIG. 11 illustrates an occupancy-based control method 1100 forresponding to the detection of a lack of occupancy in a previouslyoccupied space, performed by some embodiments of a system for managingenvironmental conditions. The method incorporates the use of a holdperiod, a grace period, and a prolong period for confirming occupancystatus. It comprises steps 1110-1160. Method 1100 may be performed bycomponents of a system 100A or 100B depicted in FIGS. 1A and 1Brespectively. In step 1110, sensor input is processed to determine if adesignated zone has transitioned from an occupied state (e.g. with atleast one occupant) to an unoccupied state (e.g. with no occupants). Thesensor input may be from one or multiple sensors and the sensor(s) maybe any type of occupancy sensor such as a motion sensor. The sensorinput may be processed by the sensor itself, or by one or more systemmodules depicted in FIG. 1A or 1B (e.g. environment manager module 110or gateway module 120). If the result of the determination is negative(e.g. no transition from occupied to unoccupied state), then no actionis taken. If the result of the determination is positive (e.g.designated zone has transitioned from an occupied to an occupied state),then a hold period is initiated, during which sensor input associatedwith the designated zone is monitored, but no change in environmentalconditions owing to the determination in step 1110 is made. At theconclusion of the hold period, a determination is made in step 1115 asto whether for the entire hold period, the sensor input indicated thatthe designated zone remained unoccupied. If the determination in step1115 is negative (e.g. the designated zone was occupied at some pointduring the hold period), then the designated zone's occupied status isnot confirmed. In many embodiments, during any point in the hold period,sensor input indicating occupancy in the designated zone would result inthe designated zone's occupied status failing to be confirmed (i.e. inthese embodiments, there would be no need for the determination of step1115 at the conclusion of the hold period). Under these circumstances,no change in environmental conditions owing to the determinations insteps 1110 or 1115 is made.

If the determination in step 1115 is positive (e.g. designated zone wasunoccupied throughout the hold period), then control transfers to step1125. In step 1125, a plurality of luminaires, lighting units, or lightsources associated with the designated zone each begin a transition to alower light level in compliance with a fade effect, and a grace periodis initiated, during which sensor input associated with the designatedzone is monitored. In many embodiments, the plurality of light sourcesis each accessible to at least one IP luminaire in the designated zone.The plurality of luminaires, lighting units, or light sources may alsobe part of the same commissioned unit, or different but linkedcommissioned units. At the conclusion of the grace period, adetermination is made in step 1135 as to whether for the entire graceperiod, the sensor input indicated that the designated zone remainedunoccupied. If the result of the determination is negative (e.g.designated zone became occupied during the grace period), then controltransfers to step 1130, and the plurality of luminaires, lighting units,or light sources that began their transitions to a lower light level instep 1125 begin transitioning back to their previous (higher) lightlevels, in compliance with a fade effect. In many embodiments, duringany point in the grace period, sensor input indicating occupancy in thedesignated zone would result in the designated zone's occupied statusfailing to be confirmed (i.e. in these embodiments, there would be noneed for the determination of step 1135 at the conclusion of the graceperiod). These circumstances indicate that the designated zone'sunoccupied status is not confirmed.

If the result of the determination in step 1135 is positive (e.g.designated zone remained unoccupied for the duration of the graceperiod), then in step 1140, the plurality of luminaires are allowed tocomplete their transition to the lower light level if the transition hasnot yet completed. Once the plurality of luminaires, lighting units, orlight sources have transitioned to the lower light level, a prolongperiod is initiated.

At the conclusion of the prolong period, a determination is made in step1145 as to whether for the entire prolong period, the sensor inputindicated that the designated zone remained unoccupied. If the result ofthe determination is negative (e.g. designated zone became occupiedduring the prolong period), then control transfers to step 1130, and theplurality of luminaires, lighting units, or light sources that begantheir transitions to the lower light level in step 1125 begintransitioning back to their previous (higher) light levels, incompliance with a fade effect. In many embodiments, during any point inthe prolong period, sensor input indicating occupancy in the designatedzone would result in the designated zone's occupied status failing to beconfirmed (i.e. in these embodiments, there would be no need for thedetermination of step 1145 at the conclusion of the prolong period). Ifthe result of the determination in step 1145 is positive (e.g.designated zone remained unoccupied for the duration of the prolongperiod), then in step 1150, the plurality of luminaires, lighting units,or light sources begin their transition to a light level associated witha switched off state in compliance with a fade effect, and a secondgrace period is initiated. In many embodiments, the amount of timeassociated with the fade effect (e.g. the time it takes for a luminaireto transition to a different light level in accordance with thecontrolling fade effect) may be automatically reset so that theluminaires, lighting units, or light sources of a commissioned unit donot transition to a light level associated with a switched off stateprior to the completion of the second grace period initiated in step1150. Alternatively, if luminaires, lighting units, or light sources ofa commissioned unit are close to completing the fade effect, and thegrace period has not yet elapsed, the luminaires, lighting units, orlight sources may wait to complete the transition until the grace periodinitiated in step 1150 has elapsed.

At the conclusion of the second grace period initiated in step 1150, adetermination is made step 1155 as to whether for the entire secondgrace period, the sensor input indicated that the designated zoneremained unoccupied. If the result of the determination is negative(e.g. designated zone became occupied during the grace period), thencontrol transfers to step 1130, and the plurality of luminaires,lighting units, or light sources that began their transitions to a lightlevel consistent with a switched off state in step 1150 begintransitioning back to their original (higher) light levels, incompliance with a fade effect. In many embodiments, during any point inthe second grace period, sensor input indicating occupancy in thedesignated zone would result in the designated zone's occupied statusfailing to be confirmed (i.e. in these embodiments, there would be noneed for the determination of step 1155 at the conclusion of the secondgrace period). If the result of the determination in step 1155 ispositive (e.g. designated zone remained unoccupied for the duration ofthe prolong period), then in step 1160, the plurality of luminaires,lighting units, or light sources proceed to complete their transition toa light level consistent with a switched off state.

Configurable Parameter: Dwell Period

Dwell period is a configurable parameter associated with occupancy-basedcontrol of environmental conditions. In many embodiments, it signifiesthe time needed for the system to ensure that a user is situated at aspace, rather than simply passing through it. When an area in questionis occupied for the duration of the dwell period, this indicates thatcommissioned unit(s) in the area in question may assume the likelihoodof more prolonged occupancy within the space and may transition toproviding a higher level of lighting. In many embodiments, the dwellperiod may range from 0 to 30 seconds, with a default value of 10seconds. Manual controllers may allow a user to alter the dwell periodwith a granularity of 1 second. The commissioning tool may be used toconfigure the dwell period for any commissioned unit, and the centraldashboard or other manual or personal controllers may be used to resetthe dwell period for one or more commissioned units.

In some embodiments, occupancy events are ignored for the duration ofthe dwell period, following the detection of a first occupancy event. Insuch embodiments, occupancy events may be monitored only are the dwellperiod expires. In such embodiments, only if occupancy is detectedbetween the moment the dwell period expires and a hold period expiresafter the dwell period, will the area in question transition to theoccupied state. Otherwise, the area will go back to being in theunoccupied state when the hold period expires.

Configurable Parameter: Smart Time

Smart time is a configurable parameter associated with occupancy-basedcontrol of environmental conditions. In many embodiments, if movement isdetected during a grace period after a hold period, following adetection of vacancy, the system assumes that the hold time was set tobe inadequately short (i.e. vacancy was concluded too soon after thelast movement detection), and the hold time is extended once by theduration indicated by the smart time parameter. In many embodiments, ifmotion is detected after an extended hold time, the hold time is notfurther extended. In some embodiments, the smart time period may rangefrom 0 to 15 minutes, with a default value of 10 minutes. Thecommissioning tool may be used to configure the smart time period forany commissioned unit, and the central dashboard or other manual orpersonal controller may be used to reset this parameter for one or morecommissioned units. In many embodiments, smart time cannot accumulate.

FIG. 12 illustrates an occupancy-based control method 1200 forresponding to the detection of occupancy in a previously unoccupied cellzone, performed by some embodiments of a system for managingenvironmental conditions. It comprises steps 1210-1250. Method 1200 maybe performed by components of a system 100A or 100B depicted in FIG. 1Aor 1B, respectively. In step 1210, sensor input is processed todetermine if a cell zone has transitioned from an unoccupied state (e.g.with no occupants) to an occupied state (e.g. with at least oneoccupant). The sensor input may be from one or multiple sensors and thesensor(s) may be any type of occupancy sensor such as a motion sensor.The sensor input may be processed by the sensor itself, or by one ormore system modules depicted, for example, in FIG. 1A or 1B (e.g.environment manager module 110 or gateway module 120). If thedetermination is negative (e.g. no transition from unoccupied tooccupied state), then control remains at step 1210 until a laterprocessing of the sensor input(s) indicates such a transition. If thedetermination is positive (e.g. sensor input indicates transition of thecell zone from an unoccupied to an occupied status), then in step 1220,in response to the determination made in step 1210, at least oneluminaire (or lighting unit or light source) transitions from notproviding illumination to providing a pre-configured background level oflight (e.g. Light Level 1) within a pre-configured reaction time period.In some embodiments the luminaire that is more closely associated with asensor sensing the change in occupancy status (e.g. the luminairehousing the sensor or otherwise physically most proximate to the sensor)transitions first to the background level of light. The at least oneluminaire may be part of a single commissioned unit or multiplecommissioned units that are scoped to or otherwise associated with thecell zone.

In step 1230, sensor input from within the cell zone is processed todetermine if a work zone within the cell zone has transitioned from anunoccupied to an occupied state. If the determination is negative (e.g.no transition of the work zone from an unoccupied to an occupied state),then control remains at step 1230 until a later processing of sensorinput indicates such a transition. If the determination in step 1230 isa positive one (e.g. sensor input indicates transition of the work zonefrom an unoccupied to an occupied status), then a dwell period isinitiated, occupancy in the work zone is monitored, and controltransitions to step 1240. Step 1240 involves monitoring occupancy in thework zone, and determining whether at any time during the dwell period,sensor input indicates that the work zone is unoccupied. If the workzone is found to be unoccupied at any time during the dwell period, thenno environmental changes are made in the work zone, the dwell period isended, and control transfers back to the step 1230. If throughout thedwell period, the work zone never became unoccupied, then controltransfers to step 1250, and at least one luminaire (or lighting unit orlight source) within the work zone transitions to a task-level of light(e.g. Light Level 2) within a pre-configured reaction time.

FIG. 13 illustrates an occupancy-based control method 1300 forresponding to the detection of a change in occupancy in a corridor zone,performed by some embodiments of a system for managing environmentalconditions. It comprises steps 1310-1360. Method 1300 may be performedby components of a system 100A or 100B depicted in FIG. 1A or 1B,respectively. In step 1310, sensor input is processed to determine ifthere is a change in a corridor zone's occupancy status. The sensorinput may be from one or multiple sensors and the sensor(s) may be anytype of occupancy sensor such as a motion sensor. If there is no changein occupancy status, then control remains in step 1310, and sensor inputmay again be processed at a later time. If the determination in step1310 indicates that there is a change in the corridor zone's occupancystatus resulting in the corridor zone being unoccupied, then controltransfers to step 1320. If the determination in step 1310 indicates thatthere is a change in the corridor zone's occupancy status resulting inthe corridor zone being occupied, then control transfers to step 1330.

In step 1320, a determination is made as to whether at least one zoneadjacent to the corridor zone is occupied. This determination may bemade by one or more commissioned units in or otherwise associated withthe corridor zone. For example, in some embodiments, a commissioned unitin the corridor zone may identify commissioned units in adjacent zonesusing its own location information and the location information of othercommissioned units. Once at least one commissioned unit in each adjacentzone is identified, their occupancy statuses may be retrieved in someembodiments by querying or otherwise retrieving the information from thecommissioned units directly. In other embodiments, a commissioned unitin the corridor zone may access the occupancy statuses of the adjacentcommissioned units from one or more remote memories associated withother system modules such as the environment manager module 110 orgateway module 130 of system 100A. The location information ofcommissioned units may be stored locally on one or more memories of thecommissioned unit in the corridor zone (e.g. cached) or stored remotelyon one or more memories remotely accessible to the commissioned unit inthe corridor zone (e.g. at one or more memories associated withenvironment module 110 or gateway module 130 of system 100A). If theresult of the determination in step 1320 is positive (e.g. at least onezone adjacent to the corridor zone is occupied), then in step 1340, nochange is made to the illumination in the corridor zone. If thedetermination in step 1320 is negative (e.g. no zone adjacent to thecorridor zone is occupied), then in step 1360, a switch off sequence isinitiated in order to transition luminaires (or lighting units or lightsources) in the corridor zone to producing no illumination.

In step 1330 a determination is made as to whether or not the level ofillumination within the corridor zone is at a predetermined minimumlevel. In some embodiments, this determination is made with respect tothe entire corridor zone, and in other embodiments, this determinationis made with respect to an area proximate to the sensor(s) producing thesensor input indicating, in step 1310, that a change occurred in thecorridor zone's occupancy status. In some embodiments, thisdetermination may be made by hardware, firmware or computer codeassociated with one or more commissioned units in the corridor zone, byhardware, firmware or computer code associated with one or more modulesof system 100A, or any combination thereof If the result of thedetermination in step 1330 is positive (i.e. illumination level ofcorridor zone is at or above the predetermined minimum level), then instep 1340, no change is made to the illumination in the corridor zone.If the result of the determination in step 1330 is negative (i.e.illumination level of corridor zone is below the predetermined minimumlevel), then in step 1350, one or more commissioned units in thecorridor zone causes the illumination level provided by one or moreassociated luminaires (or lighting units or light sources) to beincreased such that the level of illumination within the corridor zoneis increased to the predetermined minimum level within a predeterminedreaction time.

FIG. 14 illustrates an occupancy-based control method 1400 forresponding to the detection of a change in occupancy in a meeting zone,performed by some embodiments of a system for managing environmentalconditions. It comprises steps 1410-1430. Method 1400 may be performedby any combination of components of a system 100A or 100B depicted inFIGS. 1A and 1B, respectively. In step 1410, sensor input is processedto determine if there is a change in a meeting zone's occupancy status.The sensor input may be from one or multiple sensors and the sensor(s)may be any type of occupancy sensor such as a motion sensor. If there isno change in occupancy status, then control remains in step 1410, andsensor input may again be processed at a later time. If thedetermination in step 1410 indicates that there is a change in themeeting zone's occupancy status resulting in the meeting zone becomingunoccupied, then control transfers to step 1420. If the determination instep 1410 indicates that there is a change in the meeting zone'soccupancy status resulting in the meeting zone becoming occupied, thencontrol transfers to step 1430. In step 1420, a switch off sequence isinitiated in order to transition the meeting zone to producing noillumination. In step 1430, one or more commissioned units present awelcome scene. The welcome scene may require, for example, one or moretask lights to produce a higher light level, while ambient lights aredimmed In addition, decorative lighting may produce a colorcomplimenting the room's color scheme.

Daylight-Based Control

Configurable Parameters: MaxRegulationLightLevel,MinRegulationLightLevel

Using the commissioning tool, an authorized user such as a commissioningengineer may configure parameters indicative of maximum and minimumlight levels that may be achieved in an area under daylight-basedcontrol. In some embodiments, the parameters MaxRegulationLightLevel andMinRegulationLightLevel may each be set be equal to the occupancy-basedcontrol parameters MaxWhenOccupied and MinWhenOccupied, respectively.

Configurable Parameter: Daylight Harvesting

Daylight harvesting is a configurable parameter associated withdaylight-based control of environmental conditions. In many embodiments,if enabled for one or more commissioned units, it allows daylight-basedregulation of light levels in an area scoped to those commissionedunits. In many embodiments, daylight harvesting, when enabled, works tomaintain light levels in a space within a particular range (e.g.MinimumRegulationLightLevel to MaximumRegulationLightLevel).

Adjusting Illumination Set-Point—Calibrated Maximum Parameter

When a user manually configures or adjusts the illumination set-point ofa commissioned unit, a parameter of the configured unit (e.g.CalibratedMaximum) is set to the new set-point value. The commissionedunit may still be regulated based on daylight-based controls, but thenew set-point value will be used to regulate environmental conditionsassociated with the commissioned unit.

FIG. 15 illustrates a method 1500 for responding to a request for adifferent environmental scene in a meeting zone, performed by someembodiments of a system for managing environmental conditions. Itcomprises steps 1510-1530. Method 1500 may be performed by anycombination of components of a system 100A or 100B depicted in FIGS. 1Aand 1B, respectively. In step 1510, a request to provide a differentscene in a meeting room is received. In some embodiments, the requestmay be created as a result of a user selecting and requesting a scenefrom a graphical user interface displayed on an environmental controldevice 160 of system 100A, such as a smart phone. The request maythereafter be transmitted an environment manager module, such as module110 via link L2, as depicted in FIG. 1A. In some other embodiments, therequest may be generated automatically by one or more sensors sensingoccupancy in the previously unoccupied meeting zone and requesting adefault welcome scene.

In step 1520, the requested scene is accessed. A scene may be acollection of predetermined environmental parameters that transforms theenvironmental conditions in a particular zone is a prescribed way. Theenvironmental conditions affected may be, for example, lightingconditions, temperature, humidity and air flow. Each environmentalcondition prescribed in a scene may be tied to particular one or morecommissioned units or to particular types of commissioned units.Moreover, scenes may comprise very specific environmental conditions(e.g. requiring a particular commissioned unit or type of commissionedunit to produce light of a particular color at a particular intensity),or they may be specified more generally, allowing commissioned unitsinvolved in producing the scene some discretion to choose specificvalues (e.g. specifying a range of colors or a range of light levels ina particular region in the meeting room and allowing an implementingcommissioning unit to choose values within the prescribed range). Acollection of pre-configured environmental scenes may be stored on oneor more memories accessible to, for example, the environment managermodule 110 or gateway module 130 of system 100A, or any commissionedunit associated with the meeting zone referenced in step 1510. Forexample, an area controller such as area controller 420 may be such acommissioned unit capable of accessing a requested scene. In manyembodiments, such a commissioned unit may be communicatively coupled toone or more IP luminaires that control lighting conditions in variousportions of the meeting room.

In some embodiments, in step 1520, the environment control module 110 orgateway module 130 of the system may access one or more memories toretrieve details associated with the requested scene (e.g. thecollection of specified environmental conditions to be recreated inparticular areas of a space). Different predetermined scenes, eachassociated with a unique identifier, may be stored in a database, andaccessing a requested scene in step 1520 may involve matching the uniqueidentifier of the scene requested in step 1520 with the uniqueidentifier of a scene stored in the in the aforementioned one or morememories.

In step 1530, the requested scene is applied. In some embodiments,respective details of the requested scene are transmitted from a systemmodule (e.g. environment manager module 110 or gateway module 130 ofsystem 100A) to respective commissioned units (e.g. IP controller 140and 150 of system 100A) for application. For example, a scene mayrequire that all walls in a room be washed in red light of particulardimness, and all task lights in the room be dimmed up to a particularlevel. In some embodiments, these details may be codified in anenvironment control command and transmitted by the environment managermodule 110 to an area controller (e.g. area controller 320) controllingthe room in question. The area controller may thereafter transmit thecommands for changing the wall wash color to one or more IP luminairesthat provide decorative wall washes in the room, and the commands forchanging the task lighting to one or more IP luminaires controlling tasklighting in the room. The area controller may, in some embodiments, alsoprocess the commands received from the other modules such as theenvironment manager module 110, prior to communicating them to theappropriate IP luminaires (or other commissioned units) so that thecommands are compatible with a format or communication protocolunderstood by the particular IP luminaires (or commissioned units).

FIG. 16 illustrates a daylight-based control method 1600 for respondingto a detected change in illumination in a work zone, performed by someembodiments of a system for managing environmental conditions. Itcomprises steps 1610-1650. Many steps of method 1600 may be performed,for example, by components of system 100A or 100B depicted in FIGS. 1Aand 1B, respectively. In step 1610, sensor input is processed todetermine if there is a change in illumination (e.g. natural orartificial light) in a work zone. The sensor input may be from one ormultiple sensors and the sensor(s) may be any type of light sensor suchas a daylight sensor. The one or multiple sensors may detect a decreaseor an increase in light from a natural source (e.g. sunlight) or anartificial source (e.g. luminaire). The sensor input may be communicatedto and processed by one or more processors executing an environmentcontrol module such as module 110 of system 100A, a gateway module suchas module 130 of system 100A, or an area controller such as controller320 of system 300A. If there is no change in illumination, then controlremains in step 1610, and input from the sensor(s) in step 1610 mayagain be processed at a later time. If the determination in step 1610indicates that there is a change in illumination in the work zone, thencontrol transfers to step 1620.

In step 1620, a determination is made as to whether the change inillumination is greater than a pre-configured amount. In someembodiments, this determination may be made by a commissioned unit (e.g.area controller, IP luminaire) that is located proximate to thesensor(s) producing the sensor input and/or a commissioned unit that isbound to the work zone during the commissioning process. In otherembodiments, this determination is made more centrally by one or moreprocessors associated with an environment manager module such as module110 of system 100A, or a gateway module such as module 130 of system100A. If the result of the determination in step 1620 is a negative one(e.g. change in illumination is not greater than a pre-configuredamount), then no adjustment in illumination in the work zone is made.However, in some embodiments, each change in illumination that is notacted upon following step 1620 is aggregated and temporarily saved in amemory accessible to the module or modules performing the determinationsin steps 1610 and 1620. In such embodiments, step 1620 may involve usingthe running aggregate of changes in illumination over multiple previousdeterminations in step 1620 that led to negative determinations in step1620, in order to make the present determination in step 1620.

If the result of the determination in step 1620 is a positive one (e.g.change in illumination is greater than a pre-configured amount), thencontrol transfers to step 1630, and a determination is made as towhether the level of illumination in the work zone is at or above apre-configured level. In some embodiments, the determination of step1630 may be made by a commissioned unit (e.g. area controller, IPluminaire) that is located proximate to the sensor(s) producing thesensor input and/or a commissioned unit that is bound to the work zoneduring the commissioning process. In other embodiments, thisdetermination is made more centrally by one or more processorsassociated with an environment control module such as module 110 ofsystem 100A, or a gateway module such as module 130 of system 100A. Ifthe determination in step 1630 is a positive one (e.g. level ofillumination in the work zone is at or above the pre-configured level),then the illumination from at least one luminaire (or lighting unit orlight source) in the work zone is adjusted to provide a pre-configuredminimum level of illumination in step 1640. If, on the other hand, thedetermination in step 1630 is a negative one (e.g. level of illuminationin the work zone is below the pre-configured level), then theillumination from at least one luminaire in the work zone is adjusted toprovide a pre-configured maximum level of illumination. When adjustingillumination in steps 1640 and 1650 many embodiments may employ fadingin accordance with a configured fade time and/or fade speed if the fadefeature is enabled for the one or more commissioned units whose at leastone luminaire in the work zone is adjusted in steps 1640 or 1650.

FIG. 17 illustrates a daylight-based control method 1700 for respondingto a detected change in natural illumination in a space, performed bysome embodiments of a system for managing environmental conditions. Itcomprises steps 1710-1740. Many steps of method 1700 may be performed,for example, by components of system 100A or 100B depicted in FIGS. 1Aand 1B, respectively. In step 1710, sensor input is processed todetermine if there is a change in natural illumination in a designatedzone. The sensor input may be from one or multiple sensors and thesensor(s) may be any type of light sensor such as a daylight sensor. Thesensor input may be communicated to and processed by one or moreprocessors executing an environment manager module such as module 110 ofsystem 100A, a gateway module such as module 130 of system 100A, or anarea controller such as controller 320 of system 300A. If there is nochange in natural illumination, control remains in step 1710, and inputfrom the sensor(s) in step 1710 may again be processed at a later time.If the determination in step 1710 indicates that there is a change innatural illumination in the designated zone, then control transfers tostep 1720.

In step 1720, a determination is made with respect to whether the changein natural illumination is part of an increasing or decreasing trend. Anincreasing trend may be identified after multiple consecutive increasesin natural illumination are detected in step 1710 for the zone inquestion. Likewise, a decreasing trend may be identified after multipleconsecutive decreases in natural illumination are detected in step 1710for the zone in question. The number of consecutive increases ordecreases needed in order for a series of changes in naturalillumination to qualify as a trend may be a configurable parameter inmany embodiments, which may be set and/or reset using, for example, thecentral dashboard of the environment manager module 110 of system 100A.

In many embodiments, the determination of step 1720 may be made by acommissioned unit (e.g. area controller, IP luminaire) that is locatedproximate to the sensor(s) producing the sensor input and/or acommissioned unit that is bound to the zone in question during thecommissioning process. In other embodiments, this determination is mademore centrally by one or more processors associated with an environmentmanager module such as module 110 of system 100A, or a gateway modulesuch as module 130 of system 100A. If no trend is identified, thencontrol reverts to step 1710, and input from the sensor(s) may again beprocessed subsequently. If an increasing trend is found, then theillumination from at least one luminaire (or lighting unit or lightsource) in the designated zone is adjusted to provide a lower level ofillumination within a first duration (step 1740). If, on the other hand,a decreasing trend is found, then the illumination from at least oneluminaire (or lighting unit or light source) in the designated zone isadjusted in step 1730 to provide a higher level of illumination thancurrently provided by the luminaire within a second duration that isshorter than the first duration of step 1740. When adjustingillumination in steps 1730 and 1740, many embodiments may employ fadingin accordance with a configured fade time and/or fade speed if the fadefeature is enabled for the one or more commissioned units associatedwith the at least one luminaire referred to in steps 1730 and 1740.

Managing Environmental Conditions—User Triggered Controls

While many of the embodiments described in the previous sections onoccupancy and daylight-based controls focus on methods for monitoringand/or identifying patterns with respect to changes in occupancy andlighting conditions, and optimally adjusting environmental conditions torespond to these changes, this section focuses on the controls availableto users for causing changes in environmental conditions. In manyembodiments, the user may be able to override the automatic behaviordescribed in the above sections on occupancy and/or daylight-based lightmanagement.

Enabling, Disabling, and Prioritizing Control

In any given zone, all available control types (e.g. automaticallytriggered and user triggered) may be enabled or disabled. Commissionedunits may be configured such that one or more control types are enabledor disabled. Additionally, for each zone and/or commissioned unit, apriority may be associated with each type of control. When a controltype is enabled in an area or for a commissioned unit, the enabled typeof control (e.g. manual personal control, central control,occupancy-based control) may be used to issue control requests for theenabled area or for the commissioned unit. Different control types maybe enabled and operational in the same area or for the same commissionedunit. Priorities are used to resolve any conflicts or ambiguities givenall received control inputs, and to determine the environmentalconditions of any space at any given time.

Mobile Controllers

In many embodiments, mobile controllers (e.g. smartphones, tabletcomputers, and other hand-held computing devices) may be used by usersto request changes in environmental conditions. Mobile controllers maybe configured to provide visual, auditory and/or tactical feedback toits users when connecting to the environmental management system, and/ora visual, auditory and/or tactical feedback to its users within a periodof time (e.g. 0.3 seconds) from the time users request a change inenvironmental conditions. Mobile controllers may be used for personal,manual and central control of commissioned units based on their locationwithin a physical structure. For example, a smartphone may behave as apersonal controller allowing control of environmental conditions only inits user's personal or work zone when it is operated in an open zonesuch as an open office space. However, when the smartphone is in ameeting zone such as a conference room, it may behave as a manualcontroller allowing its user to control environmental conditions in theentire meeting zone.

Power Up Behavior

FIG. 19 illustrates a method 1900 for determining the power-up behaviorof a commissioned or uncommissioned unit, performed by some embodimentsof a system for managing environmental conditions. The method may, forexample, be performed by a group of luminaires, an IP luminaire such asIP luminaire 150 of FIG. 1A, a sensor or group of sensors, a camera orgroups of cameras, or any controllable device. The method may also beperformed by computer code executing on one or more processors locatedremotely from one or more devices whose power up behavior is to bedetermined.

Method 1900 comprises steps 1910 through 1970. Step 1910 involvesdetermining whether or not a device or unit in question is commissioned.The process of commissioning was previously described, for example, inthe context of FIG. 5. In some embodiments, during the commissioningprocess, one or more memories may have been updated to reflect thecommissioning status of the device or unit in question. Determiningwhether the device or unit in question is commissioned may thereforeinvolve accessing the one or more memories. In some embodiments, adevice or unit itself may store information regarding its commissioningstatus. In such embodiments, determining whether or not a device or unitis commissioned may involve the device itself or computer code executingoutside of the device, accessing the device's stored commissioningstatus or information reflective of its commissioning status.

If it is determined that the device is commissioned, then controltransfers to step 1920. Otherwise, control transfers to step 1930. Bothsteps involve determining whether or not the device or unit in questionhas network connectivity. In some embodiments, this can be carried outby a device or unit performing a test to determine if connectivityexists. In other embodiments, this may be determined, for example, bycomputer code associated with a system module such as environmentmanager module 110 or gateway module 130 of system 100A, performing thenecessary test(s).

If it is determined in step 1920 that the commissioned unit has networkconnectivity, then control transfers to step 1940. Step 1940 involvesretrieving and applying system power-up configuration parameters for thecommissioned unit. The parameters may be stored centrally on a server orother device accessible to the device or system module performing step1940, or at the commissioned unit itself. If power-up configurationparameters are stored in multiple places, step 1940 may also involvedetermining which set of parameters take precedence. In someembodiments, if the commissioned unit is a luminaire, a default behaviorat power-up may be produced. For example, within 0.3 seconds, theluminaire (or lighting unit or light source) in question may produce alight level equal to the light level the luminaire (or lighting unit orlight source) is configured to produce shortly before power-down.

If it is determined in step 1920 that the commissioned unit does nothave network connectivity, then control transfers to step 1950. In step1950, locally available system power-up configuration parameters areapplied for the commissioned unit. For example, there may be a set ofpower-up configurations stored at the commissioned unit itself, whichare accessible to the commissioned unit without the need for networkconnectivity.

If it is determined in step 1930 that the non-commissioned unit hasnetwork connectivity, then control transfers to step 1960. In step 1960,default power-up configuration parameters are applied if no overridingpower-up configuration is available via the network. Default power-upconfiguration parameters may reside on the network outside of thenon-commissioned unit, or on the unit itself For example, if thenon-commissioned unit is a luminaire (or lighting unit or light source),the default power-up configuration may require a light level at 100% ofthe luminaire's capability to be produced within 0.3 seconds ofpower-up.

If it is determined in step 1930 that the non-commissioned unit does nothave network connectivity, then control transfers to step 1970. In step1970, default power-up configuration parameters stored locally on thenon-commissioned unit or otherwise available to the non-commissionedunit without network connectivity may be applied to the non-commissionedunit.

According to some embodiments involving non-commissioned luminaires thatare installed and powered but not connected to an IP network, thefollowing behavior may be realized. Each luminaire (or lighting unit orlight source) may go to producing light at 100% of its capability within0.3 seconds from the moment of powering on, and each such luminaire mayignore any control commands from control devices that instructotherwise. In some embodiments, if the non-commissioned luminaires areinstalled, powered, and connected to an a communication/control line ofan IP network, all luminaires of the IP sub-network may go to producinglight at 100% of their capabilities within 0.3 seconds from the momentof powering of the sub-system. These luminaires may ignore sensorinformation (e.g. occupancy and daylight sensor information), but reactto manual control (e.g. from area IR controllers) as well as to centralcontrol commands (e.g. from the environment manager module 110,commissioning module 120, or gateway module 130 of FIG. 1A).

According to some embodiments involving commissioned luminaires (orlighting units or light sources), the following behavior may be producedat power-up. To demonstrate functionality, such units may go toproducing a configured maximum light level within some time interval(e.g. 2 seconds) after the system has been powered on. In suchembodiments, if there is no presence detected in the area of thecommissioned luminaires subsequent to the powering on, the commissionedluminaires will switch off within another time interval (e.g. 1 second)following a determination that no presence was detected. In some otherembodiments involving commissioned luminaires, such luminaires may notproduce any light after being powered up until occupancy in the area ofthe luminaires is detected for some configured period of time.

Reaction Times

Different reaction times are related to users' expectations whenrequesting an environmental change, such as a change in lightingconditions. If a fade parameter associated with a commissioned unit orthe user herself (e.g. a user preference parameter indicating whether ornot the user prefers a fade effect) is disabled, then the requestedchange in the environmental condition (e.g. light level adjustment)should be immediate. If fade is enabled, then the requested change inenvironmental conditions may start within a time interval (e.g. 0.3seconds) from the moment of the change request.

Another configure related to reaction times is fade time, or the timeinterval during which a first environmental condition (e.g. a presentlight level) fades to a second environmental condition (e.g. a newrequested light level). In many embodiments, Fade time is a value setbetween 0.5 and 90 seconds. Manual controllers that allow a user tocontrol fade time may allow the user to increase or decrease the fadetime with a particular granularity (e.g. increases or decreases of fadetime allowed in 1 second granularity). The fade and fade time featuresare comfort features designed to result in changes in environmentalconditions that are smooth, less jarring and therefore less noticeableand less distracting.

Control Overrides

FIG. 20 illustrates a method 2000 for handling a control request,performed by some embodiments of a system for managing environmentalconditions. Method 2000 comprises steps 2010 through 2050. One or moresteps may be omitted in performing the method, and other steps notdepicted may also be added. In some embodiments, the method may beperformed by a commissioned unit itself, computer code executing on oneor more processors communicatively connected to commissioned unit (e.g.at processors associated with environment manager module 110 or gatewaymodule 130 of system 100A) or any combination of thereof. In step 2010,a control request is received. The control request may be a request tochange an environmental condition (e.g. light level, temperature orhumidity), and may arise due to a variety of circumstances. For example,a user may request a change using an environment control device such asdevice 160 of system 100A, a wall mounted user interface device, or auser interface (e.g. central dashboard) provided, for example, by theenvironment manager module 110 or gateway module 130 of system 100A. Acontrol request may also be generated as a result of changes inoccupancy or daylight in an area. For illustrative purposes only, let usassume that a user has used a wall-mounted manual controller in a roomto request a higher level of light, and that the manual controller islinked to a particular commissioned unit in the room.

Step 2020 involves determining whether the requested control option isenabled. In many embodiments, all available control options (e.g.occupancy-based control, daylight-based control, manual, personal, andcentral control) may be disabled, enabled and/or prioritized percommissioned unit. In the example being used for illustrative purposes,step 2020 involves determining whether the manual control is enabled forthe commissioned unit linked to the manual controller being used torequest a change in lighting conditions.

If step 2020 results in a negative determination (i.e. the controloption is not enabled for the associated commissioned unit), thencontrol transfers to step 2030, and the received control request isignored. If step 2020 results in a positive determination (i.e. thecontrol option is enabled for the associated commissioned unit), thencontrol transfers to step 2040.

Step 2040 involves determining whether or not there is a competingcontrol request of higher priority that should override the receivedcontrol request. If step 2040 results in a negative determination (i.e.no competing control request of a higher priority is found), thencontrol transfers to step 2050, and the requested control is performed.Otherwise, if step 2040 results in a positive determination (i.e. acompeting control request of a higher priority is found), then controltransfers to step 2030 and the received control request is ignored. Forexample, an automatic request arising out of daylight-based monitoringof space surrounding the commissioned unit may indicate a request toadjust the luminaires (or lighting units or light sources) associatedwith the commissioned unit to provide a lower light level than thatrequested by the user's request arising out of his/her use of a manualwall-mounted control. In such a case, if the commissioned unit has ahigher priority for manual control as compared to daylight-basedcontrol, then the luminaires associated with the commissioned unit willadjust the illumination they provide to produce the manually-requestedlevel of illumination.

Manual Control

Manual control refers to the means available to a user for manuallyaltering environmental conditions. During the commissioning processdepicted in FIG. 5, units may be commissioned to be manually controlled.The commissioning and configuration may include linking of userinterfaces for manual control to commissioned units, linking of userinterface elements (e.g. buttons, sliding bars) to presets (e.g. scenes,light levels). During commissioning, manual control may be enabled ordisabled for a unit being commissioned, and/or manual control may beassigned a priority level as compared to other types of controls.Commissioned units that have manual control enabled may also have otherforms of control enabled (e.g. daylight-based and occupancy-basedcontrols).

Manual control enables a user to manually turn on or off commissionedunits. For example, an end user may enter an indoor space such as a roomand using a wall-mounted display or switch or a user interface on ahand-held device, turn on luminaires associated with one or moreluminaires in the room. Such a manual request may result in theluminaires producing a pre-configured level of light (e.g. going to aswitch on level of light). If prevailing environmental conditions, suchas the level of lighting in a space, are not what a user desires, he orshe may manually adjust the lighting using a manual control, byindicating that the lighting in the space be dimmed up or down. Such amanual request may result in luminaires in the space adjusting theirlight output by a pre-configured percentage. Many embodiments mayrequire that fixed manual controllers be placed in a visible locationwithin the space it controls, and that the manual controller shall notbe able to control environmental conditions in a space where the userrequesting the manual changes would not be able to physically sense(e.g. see, feel or hear) the changes requested using the controller.

In some embodiments, manual changes that are requested from a mobilecontroller (e.g. a smartphone) are required to be activated within alonger duration of time (e.g. a scene change in a meeting room that isrequested from an iPhone need only be activated within 3 seconds of therequest), as compared to manual changes requested from a fixed mobilecontroller (e.g. a wall-mounted controller). For example, a scene changein a meeting room requested from a wall-mounted control device may needto be activated within 0.3 seconds of the request in order to create asense of instantaneous response to the request. This difference may beinstituted in a system such as system 100A or 100B in order to satisfyusers' expectations that environmental changes initiated in a spaceusing manual wall-mounted controls be instantaneous.

In many embodiments, commissioned units may store multiple presets thatmay be manually requested. In other embodiments, these presets mayadditionally or alternatively be stored at one or more remotely locatedmemories. For example, one preset may be a lighting scene, which causesmultiple commissioned units to each produce a preset level of light.Such a preset may result in a lighting “effect” in a space, such as dimlights in various parts of the room and bright lights in others. In someembodiments a preset light level may be configured by specifyingabsolute light levels or relative light levels (e.g. 5% dimmer than theswitch on light level), or by an algorithm that takes into considerationa variable parameter such as the amount of natural light available.

Back to Default

In various embodiments, a user may be able to undo a manually selectedenvironmental condition, and cause the conditions to revert back to aprevious or default setting. For example, a user may use a manualcontroller to de-select or cancel a previously requested light level orlighting scene. This feature enables the user to “switch off” a personallighting or other environmental condition at any time. One or morecommissioned units participating in providing the requested light levelor scene may then return to a previous configuration or a default state.

Configuration Parameter—Manual Retention Time

In many embodiments, the configuration of a manual retention timeparameter allows for the resetting of environmental conditions to be incompliance with manually-requested conditions, even after commissionedunits previously applying the conditions have stopped complying with themanually-requested conditions. The need for this parameter may occur invarious circumstances. For example, in some situations, a user may entera previously unoccupied room, where lighting conditions were beingautomatically adjusted based on the presence of natural light. The usermay thereafter utilize a manual controller to request that commissionedunits in the space produce a particular level of light in the space,regardless of the amount of natural light present, thereby effectivelyoverriding the automatic daylight-based control of the space. Under suchcircumstances, when the user leaves the room, automatic daylight-basedcontrol of the room may resume or the lighting in the room maytransition to a switched off state after an appropriate amount of timehas elapsed. In embodiments where a manual retention time is beingapplied, the commissioned units in the room may return to providing thelight levels manually requested by the user if the user is detected tohave re-entered the same space within the manual retention time period.In many embodiments, the manual retention time period begins elapsingimmediately following the time when the commissioned units in questiontransition to providing environmental conditions that differ from theuser's manually-requested conditions. In many embodiments, the manualretention time may be automatically set at 15 minutes.

Configuration Parameter—Dimming Step

Dimming step is a configurable parameter that is associated withuser-based light control. Each commissioned unit may have an associateddimming step parameter and manual and personal controllers may also haveassociated dimming step parameters. In many embodiments, this parameteris expressed as a percentage and may range from 5% to 30%.

A user may choose to set the dimming step at 10% for a commissionedunit. In such a case, when the commissioned unit is dimmed once (e.g. byone step), the light output of the commissioned unit is reduced by 10%of its previous output. In some embodiments, the dimming step is set to5% by default. Many embodiments may also permit the user to alter thedimming step but by only a particular level of granularity (e.g. 5%).This parameter may be used as a mechanism to control the speed withwhich a user may manually dim lighting in a space.

Personal Control

Person control refers to the means available to a user for controllingthe environmental conditions in their personal space or work zone.Devices providing personal control may be linked to one or morecommissioned units during the commissioning process of FIG. 5. Personalcontrol devices may be stationary (e.g. wall-mounted devices) or bemobile (e.g. smart phones or other hand-held devices). In manyembodiments, a personal control device that is stationary may only belinked to commissioned units that are located within a limited radius ofthe personal control device. Mobile personal control devices may belinked to multiple commissioned units that are more geographicallydispersed throughout a space. In some embodiments, when a user uses apersonal control device to control environmental conditions such aslighting in their work zone, the personal control request may affect thebehavior of only the commissioned units that are both linked to thepersonal control device and present in a work zone associated with theuser's present location. A personal control request to alterenvironmental conditions in a user's work zone may arise automatically(e.g. from occupancy-based control methods) or manually (e.g. from auser using a manual or personal control device to request a change inenvironmental conditions). Daylight-based and occupancy-based control ofenvironmental conditions may affect and/or be affected by the personalcontrol of commissioned units that are also configured to able torespond to personal control requests for environmental changes.

For example, if a user wishes to increase the light level in a work zoneto a particular level, but the ongoing daylight-based control of thelighting in the work zone does not permit increasing the light level inthe work zone to the particular level, the light level in the work zonemay only be permitted to increase to a different lower level. In manyembodiments, whether or not a user is able to use a personal controllerto control lighting in his/her work zone depends on whether or not theuser has permissions to affect environmental conditions in the workzone. Permissions for authorizing users to control conditions in theirwork zones may be stored at commissioned units, and/or more centrally atone or more memories accessible, for example, to system modules such asenvironment manager module 110 or gateway module 130 of system 100A.

Commissioned units may be configured to behave in particular ways inresponse to personal control requests. For example, all luminaires (orlighting units or light sources) associated with a commissioned unit maybe configured to provide 500 lux on a reference surface when a personalcontrol device is used to request a particular scene for a particularwork zone. There may also be one or more personal control modesassociated with commissioned units and/or personal control devices. Forexample, a limited set-point mode may prevent a user from dimming beyonda maximum calibrated light set-point. An unlimited set-point mode maynot impose such restrictions.

Commissioned units that typically adjust behavior based on controlrequests may be commissioned to enable or disable personal controlrequests. Such units may also assign a priority level to personalcontrol requests. Additionally and/or alternatively, personal controldevices themselves or users using the devices to create personal controlrequests may assign priority levels to personal control requests.

Personal control devices such as smart phones running personal controlapplications may be used by users to graphically view the zones and/orcommissioned units that are under the control of the device. In someembodiments, any response to such requests may be required to be madewithin a configured amount of time (e.g. 3 seconds). Failure to respondwithin the allotted time may result in an error being reported by thepersonal control device itself to one or more modules of the system(e.g. environment manager module 110 or gateway module 130 of system100A). Alternatively, in various embodiments, if a response to a userrequest made via a personal controller takes longer than a configuredamount of time, then the user may be given feedback on the progress ofthe request (e.g. a progress bar or other visual or auditorynotification).

Scene Selection and Light Tuning

Using personal controls, users may select preconfigured scenes for theirwork zones. For example, a user may select a standard scene where alllighting units associated with a commissioned unit providing light forthe user's work zone switch to a particular light level. A user may alsouse personal controls to control the dim level of luminaires (orlighting units or light sources) associated with commissioned units.Commissioned units may be configured to provide illumination within adetermined range (e.g. between a minimum light output and maximum lightoutput), and a user's ability to control the dim level of such units maybe confined to controlling output within such a range.

In some embodiments, manually-made environmental change requests mayresult in changes in environmental conditions which are thereaftercontrolled automatically. For example, if a manually-made personalrequest results in providing a fixed level of light in a space,automatic controls may regain control of the space after certain eventsoccur (e.g. the space is determined to be vacant). In some embodiments,the manually-made change in conditions may be thereafter managed byautomatic controls even without requiring that a particular event occurprior to transfer of control to the automatic means.

FIG. 21 illustrates a method 2100 for handling a manually-activatedpersonal control request, performed by some embodiments of a system formanaging environmental conditions. Method 2100 comprises steps2110-2150, which may be performed in an order different from thatdepicted. Steps may be omitted, and other steps may be added. In step2110, a manually-activated personal control request is received. Invarious embodiments, the request may be received by a system module suchas environment manager module 110 of system 100A depicted in FIG. 1, anda user may use a smartphone to issue the request. In some embodiments,the user may increase or decrease a current temperature set point toanother set-point that is within a configurable range (e.g. within 2degrees Celsius of the current set-point). The user interface being usedto request the increase may permit increases or decreases according to aconfigurable level of granularity (e.g. increases or decreases in 0.1degree Celsius steps may be permitted). In many embodiments, therequested adjustment of temperature may affect the HVAC areas associatedwith one or more commissioned lighting units in the user's work zone.

In step 2120, a determination is made on whether the user issuing therequest is authorized to make the requested changes in environmentalconditions. In some embodiments, this determination is made by one ormore system modules such as environment manager module 110 or gatewaymodule 130 of system 100A. The determination may be based on the user'slocation and/or identification (e.g. user ID and password) information.In embodiments that use a user's login information (e.g. user ID andpassword) to verify authorization, the user may have to provide his/hercredentials only once unless he/she has been logged out since the lasttime the user's credentials were verified. If the user is not authorizedto alter environmental conditions in accordance with the request,control transfers to step 2130, in which the personal control request isignored. In the user is not authorized to alter environmental conditionsin accordance with his/her request, he/she may be notified of this fact.If user authorization is additionally or alternatively dependent on theuser's location, the location information may be cached for aconfigurable period of time, thereby avoiding the need to update thesame user's location every time he/she requests a change inenvironmental conditions.

If the user is authorized to make the requested environmental changes,one or more commissioned units may be instructed to adjust environmentalconditions in accordance with the personal control request in step 2140.For example, luminaires (or lighting units or light sources) associatedwith one or more commissioned units controlling lighting conditions inthe user's work zone may transition to producing a requested level oflight in the user's work zone (e.g. reference surface) in accordancewith a configured fade time. In many embodiments, control then transfersto step 2150, in which the control of environmental conditions revertsback to automatic controls. For example, the light output produced bythe one or more commissioned units associated with the user's work zonemay thereafter revert to being controlled in accordance with previouslyused daylight-based and/or occupancy-based algorithms.

In many embodiments, personal controllers may allow authorized users toselect or otherwise specify the geographic scope of their personalcontrol. If the user making this scope selection is using his/her ownpersonal controller device (e.g. a smartphone), information identifyingthe user may be linked to the scope selection and/or other profilesettings of the user automatically, without requiring further input fromthe user. If, on the other hand, the user making the scope selection isusing a publicly accessible personal controller device (e.g. acontroller affixed to a wall in a space accessible to multiple users),the user may have to identify him/herself in order to link his/her scopeselection to his/her identity within the system for managingenvironmental condition. Once a user successfully selects or specifies ageographic scope of personal control, environmental control requestsaffecting an area within the same geographic area, but received fromusers outside the geographic area, may be ignored.

Personal Settings and Recall of Previously Applied EnvironmentalConditions

Many embodiments enable a user to recall light settings or otherenvironmental conditions previously requested. These settings orconditions may have been previously requested by the same userrequesting the recall, or by other users of the same space. Commissionedunits may store previously requested settings themselves and/or settingsmay be stored more centrally in one or more memories accessible to, forexample, system modules such as environment manager module 110, gatewaymodule 130 and/or commissioning module 120 of the system 100A.Previously requested environmental conditions may be associated withparticular users, zones, and/or commissioned units.

Central Control

Central control refers to the means available to a user for performingscheduled or real-time adjustments to system parameters that may affectenvironmental conditions within a space in a more global or pervasiveway. Central control also refers to the control of environmentalconditions using a user interface executed by a system module such asthe environment manager module 110 or gateway module 130 of system 100A.Central control may be manual (e.g. a user manually adjusting lightsettings using a displayed user interface), or automatic (e.g.adjustments to environmental conditions occurring as a result of systemreactions to detected events). In many embodiments, to centrally controlone or more commissioned units within an area, the commissioned unitsneed to be communicatively connected to a central dashboard. The centraldashboard comprises computer code executing one or more user interfacesthat allow authorized users to control various commissioned units,groups of commissioned units and/or entire zones within a physicalstructure. In many embodiments, the central dashboard may also becommunicatively connected to and/or executed by one or more modulescentral to the operation of the systems for managing environmentalchanges described herein. For example, in many embodiments, the centraldashboard is executed by or in conjunction with the environment managermodule 110 or gateway module 130 of system 100A. In various embodiments,the central dashboard may be used to re-commission and/or re-configurecommissioned units. In some of these embodiments, the user interface(s)of the central dashboard may display the reconfigurable parameters alongwith their present values or statuses, and prevent the user of thecentral dashboard from configuring parameters that are notre-configurable or setting parameters of commissioned units to valuesthat are outside of permitted ranges.

Scheduled and Real Time Central Control

A user may utilize a centralized utility such as the central dashboardto alter settings of commissioned units in order to affect environmentalconditions in real time or in a scheduled manner. Real time requests areprocessed such that resulting changes in environmental conditions aremade within a configurable amount of time following the request. Thecentral dashboard may also be used by appropriately authorized users(e.g. a facility manager) to alter parameters that affect overall systembehavior such as the configurable amount of time within which real timerequests need to be serviced.

Creating and Managing Schedules

The central dashboard may be used to create, edit and schedule tasksembodying changes in environmental conditions. Tasks may be scheduled tobe triggered at specific times (e.g. at specific time intervals, at atime relative to an event, or at an absolute time), or upon theoccurrence of a specific event. A task may specify changes that are moreglobal in nature by, for example, resetting a parameter that affectsmultiple areas or commissioned units (e.g. changing a fade time, holdtime, enabling or disabling a type of control). A task may also specifychanges that are more local in nature by, for example, reducing thelight output of a commissioned unit that only affects a particular workzone. During the commissioning process, an authorized user such as afacility manager may create and schedule default tasks. For example, anight task may be triggered to be executed after work hours and maychange hold times and default light levels in order to conserve energy.

A scheduled task may comprise a series of tasks that are themselvesscheduled to be performed at certain times, upon the occurrence ofcertain events and/or in compliance with certain logic. Users may selectexisting schedules for application. The same schedules may be repeatedlyapplied. Accordingly, the central dashboard may provide user interfacemeans for selecting one or more schedules for application, specifyingthe scope of schedules (e.g. the commissioned units or zones on whichthe selected schedules will be active), what events will triggerschedules (e.g. time of day, environmental condition, user activity),and/or the frequency with which the schedules are to be applied (e.g.one time only, a few times a day, whenever a triggering event occurs).

Schedules may also be activated immediately. In such cases, tasks in theschedule in question may take effect within a predetermined amount oftime (e.g. within 5 seconds). Examples of tasks include changing thelight output for a luminaire or commissioned unit (e.g. dimming up/downfrom a current light level, going to a particular dim level, recallinglight scenes, switching off/on), reconfiguration of control parameters(e.g. enable/disable a control option, change a sensor hold time, changea fade time), changing the temperature in an area, running an emergencylighting test, and performing auto-calibration of selected sensors. Inmany embodiments, scheduled tasks may also involve database relatedtasks, such as rolling data from commissioned units (e.g. diagnosticslogging, energy consumption data), sending reports or notifications todifferent system modules, and backing up specific data or categories ofdata.

In many embodiments, only one schedule may be active with respect to thesame commissioned unit at any given time. Transitioning between settingsof two consecutive tasks in a schedule may involve a fading transitionwithin a fade time. Accordingly, creating and/or selecting schedules mayinvolve specifying or selecting parameters such as a fade time and/orenabling or disabling a fade transition between tasks in a schedule.

Creating and Configuring Alarms

The central dashboard or a user interface associated with thecommissioning module may allow an authorized user such as a facilitymanager to create and configure alarms. An alarm may be any means bywhich one or more modules, controllers or devices associated with thesystem for managing environmental conditions within a structure isnotified of system statuses that are abnormal or may otherwise requireaction. An alarm may be associated with various configurable parameters.These parameters may be manually set or altered by an authorized user,or automatically updated during system operation. An alarm may have anassociated type (e.g. an error or a warning). An alarm may indicate itssource, or the event or condition that generated the alarm. Examples mayinclude a change in a system status, a particular system status, or ascheduled or unscheduled event occurring. An alarm may also have anassociated destination (e.g. a user account that must be notified aboutthe alarm), a scope (e.g. commissioned units the alarm potentiallyaffects), a format (e.g. SMS, e-mail, audio, visual, tactical), atrigger (e.g. a schedule or task that the alarm invokes), and a triggercondition that causes the alarm to be invoked (e.g. time, system status,change in system status, or a scheduled activity). Alarms may also causeparticular data to be displayed on the central dashboard in order tovisually present alarm data to responsible personnel. Examples includethe location of the commissioned unit, device, or environmentalcondition causing the alarm, an indication of the severity of the alarm,and an indication of the status of the alarm (e.g. whether or not it isbeing handled).

Central Control Override

In some embodiments, an authorized user may use the central dashboard toissue an overriding central control command or otherwise configure thesystem for exclusive central environmental control, such that all otherautomatic or user-generated environmental control requests are blockedor ignored until the particular overriding central command or otherevent completes, or is manually ended. Such a central control overridemay be used during emergencies, such as during a building fire or abreach of security.

Central control may also take into account manually-requestedenvironmental conditions that are in effect in various areas. Forexample, although the central dashboard may allow a facility manager toeasily alter lighting conditions in a large open plan office area, thefacility manager may wish to skip over areas that are under personalcontrol of other users. In some embodiments, this is accomplished byusing information about the different lighting conditions in variousparts available in real time to system modules such as the environmentmanager module 110 or gateway module 130.

In many embodiments, a centrally-issued environmental control requestthat comes before or after a personal or manual control request may notaffect the system's response to the personal or manual control request.For example, a central control request to switch a commissioned unit toa lower light level may result in the commissioned unit producing thelower light level. However, a personal or other manual control requestmay thereafter successfully switch the commissioned unit to produce ahigher light level.

Back to Default Behavior

In many embodiments, a central control request may be issued to takeeffect in a space, and prevent other control requests from taking effectin that space until it is manually deactivated. To prevent a situationwhere a facility manager may inadvertently fail to deactivate such anoverriding central control, automatic controls may override such centralcontrols under some limited circumstances, such as when the systemrecognizes that the space is vacant. Under such circumstances,occupancy-based control may replace the central control of the space,and environmental changes in accordance with the occupancy-based controlmay take effect.

Load Shedding

In many embodiments, the central dashboard allows an appropriatelyauthorized user (e.g. a facility manager) to cause the system to switchto a predefined load shedding mode. Such modes may be designed to savepower by automatically causing various system-wide parameters to bealtered, as well as causing various commissioned units to react inparticular ways. For example, all personal controls may be disabled, allluminaires (or lighting units or light sources) in selected areas may bedimmed or switched off, and all hold times and grace periods forautomatically triggered controls such as occupancy-based controls may beshortened.

Graphical User Interfaces

Customization of Views

The environmental control systems described herein provide a variety ofdifferent graphical user interfaces (GUIs) for facilitating interactionwith users. Exemplary embodiments of three categories of such GUIs aredescribed below. In additional, a customization graphical user interface(customization GUI) is provided that allows a user to create customizedGUIs. A user may use the customization GUI to create GUIs for use inparticular tasks (e.g. dimming luminaires associated with commissionedunits in different rooms) or in particular areas the user frequents(e.g. a GUI that displays monitoring information for commissioned unitsin three rooms that the user is interested in). The customization GUImay also be used to create different views based upon the user's role(e.g. a user with a role that requires monitoring power consumption) maybe provided a set of graphical views of a room where the powerconsumption information is highlighted or otherwise accessible withfewer clicks or interactions from the user. Based on the user's roleand/or preconfigured profile of preferences, the customization GUI maysuggest various custom views (e.g. overhead view of the user's celloffice and surrounding area) comprising various details (e.g.temperature and humidity conditions in the cell office). While preparingone or more custom GUIs using the customization GUI, the user may chooseto add or remove various details in order to achieve a custom GUIrepresentative of the user's own preferences.

Central Dashboard

System modules may also allow a user to customize the GUI of the CentralDashboard Home Page according to the user's needs. For example, it maybe possible for a user to create different views based on his/her role(e.g. end user of office space or facility manager). A facility managermay be presented with maintenance data as well as energy consumptiondata, while an end user may only be presented with energy consumptiondata and data on current environmental conditions (e.g. temperature,light levels), but not maintenance data.

The Dashboard GUI may also present (e.g. on the floor plan itself or ona side panel), operational statuses of various commissioned units (e.g.if an unresolved error has been reported for a unit, if a unit is turnedon or off). In many embodiments, data regarding devices such as theirfunctions or status data is presented to the user within 0.5 seconds ofbeing requested by the user (e.g. by placing the cursor over the deviceon the floor plan). The devices may also be visually highlighted on thefloor plan. The Dashboard GUI may also visually depict differentcategories of devices or commissioned units on the floor plandifferently. For example, different icons may be used to visually depictlighting devices, HVAC devices, sensors, and control devices. The choiceof icons may be customizable to the user's preferences. Differentinformation may be presented for a commissioned unit depending on itscategory. For commissioned units used for lighting, the information maycomprise the current light level, and energy usage, and whether or notoccupancy-based or daylight-based control is enabled. For sensors, themeasurement of the last sensed data, or an average of measurements overa particular recent time period may be presented.

The Central Dashboard GUI may also provide the user the ability tochange parameters for commissioned devices. When the user selects acommissioned device, its parameters may be displayed, and the editableparameters, based on the user's permissions and/or role, may be visuallydisplayed as being editable. Parameters that the user is not allowed toedit may be visually presented as being non-editable (e.g. grayed out).The acceptable range of a parameter may also be indicated and parametervalues outside of the range may not be accepted by the central dashboardGUI. Help tips may also be available through the central dashboard GUI.For example, help tips may be presented as an overlay when the user'scursor hovers on a commissioned unit. Some embodiments of the centraldashboard GUI may be available in languages other than English. TheCentral Dashboard GUI may also provide graphical means for a user tomanage schedules. An authorized user may use the Dashboard GUI tocreate, edit, delete, prioritize and otherwise manage schedules.

The central dashboard GUI may also provide graphical means to centrallycontrol operational settings of commissioned units throughout thesystem. For example, users may control light settings for a group ofselected commissioned units or individual commissioned units in realtime (e.g. by using graphical means to select multiple commissionedunits and/or individual luminaires and select new light levels or dimlight output by one or more steps). The new operational states (e.g. newillumination levels) may thereafter be visually reflected on the centraldashboard as feedback to the user that the changes have taken place.

System modules or commissioned units themselves may also conductanalysis of available monitoring data to provide system modules such asthe environment manager module 110 of system 100A recommendations onparameter settings that lead to optimal system performance (e.g. energyefficient performance). These recommendations may be presented to theuser at the time he/she is presented with user interface means foradjusting operational parameters for commissioned units. Real timeanalysis of estimated energy usage and energy savings may be conductedand presented to the user, along with cost estimates, to help the userdetermine optimal parameter settings.

Monitoring Dashboard

The Central Dashboard (GUI) may also comprise a Monitoring Dashboard GUIthat displays data collected by various components of the system (e.g.environment manager module 110, gateway module 130, IP luminaire 150, orarea controller 320). The data collected (referred to herein generallyas monitoring data), may be data reflecting, for example, space usage(occupancy, presence), energy consumption, temperature, humidity, carbondioxide levels, usage of automatic controls and manual controls, anddetected operational errors. Energy consumption data may be captured asactual energy measurements or notional energy measurements. Energyconsumption may be measured in KWh. Each collected data sample may beassociated with a time stamp, and a device identification or physicallocation. Presence may be recorded as a yes/no per commissioned unit(s)or areas in question; and occupancy may be recorded as a percentage ofthe time the commissioned unit(s) or areas in question are occupied.Occupancy status may be concluded based on multiple sensors associatedwith a commissioned unit. The generation of maintenance and diagnosticmessages or reports may also be monitored and recorded. For example,alarms or alerts generated by commissioned units in the form of messagesreporting operational errors or warnings may be monitored to predictpotential future malfunctions.

The monitoring data may be presented in graphical form, and may beanalyzed using any combination of standard and proprietary analyticalmethods. In many embodiments, the monitoring data may allow users suchas facility managers to gain valuable insights into trends in the data,make comparisons with previously gathered data (e.g. historical data)and to implement strategies such as energy consumption strategies basedon the data.

Commissioned devices being monitored may store monitored data on thedevice itself or the data may be stored in one or more memories (e.g. adatabase) accessible to system modules such as the environment managermodule 110, commissioning module 120 or gateway module 130 of system100A. Monitoring data may be logged at specified configurable timeintervals. Additionally the occurrence of events (e.g. detection ofoccupancy) may cause monitoring to stop or resume. When monitoringoccurs can be expressed by one or more configurable parameters on asystem-wide basis (e.g. by the setting of system-wide parameters orrules affecting multiple areas and commissioned units) or on adevice-by-device basis.

Monitoring Data and Presenting Monitored Data

The Monitoring Dashboard may allow an authorized user to select theinformation to be monitored, the spatial and temporal granularity withwhich the monitored data should be collected, the space(s) that shouldbe monitored, analytical tools that should be applied to the data,and/or the visual presentation of the raw or analyzed data. Some users(e.g. facility managers) may have the authorization to select new areasfor monitoring or to stop gathering data in other areas. Other users(e.g. office users) may be able to specify what types of monitoring datathey view on the Monitoring Dashboard, or whether or not they view rawor analyzed monitoring data, but may not be able to affect thecollection of the monitoring data itself.

Users may select areas (e.g. the campus, the building, particularfloors, rooms or work areas) or particular commissioned units or typesof commissioned units for monitoring from an interactive floor map.Users may also specify or select how much monitoring data they wouldlike to access (e.g. a whole year, 6 months, 1 month, 1 week, 1 day),and how recent the data should be (e.g. in the past month, week, day,hour). Depending on the type of monitoring data, the temporalgranularity of the available data may vary.

The user may also be able to configure the presentation of themonitoring data. For example, the Monitoring Dashboard may allow usersto select the type of graph(s) used to present raw or analyzed data(e.g. heat maps), or choose other details affecting visual presentation.For example, a user may configure their own monitoring view to use aparticular color code to indicate occupancy status (e.g. red for areasthat are occupied more than 90% of the time during working hours, greenfor areas occupied less than 20% of the time during working hours). Theuser may also be able to generate reports based on collected monitoringdata. Reports may be customizable and exportable in many formats such aspdf, doc, xls, and XML.

As user comfort is very important to the systems herein for managingenvironmental conditions within a structure, the monitored data includeskey indicators of this metric. For example, the number of manual orpersonal overrides of prevailing environmental conditions associatedwith commissioned units or areas may be tracked over time. This includesmanual changes in light levels, and manual changes in temperature,humidity, and air flow. These changes may be analyzed in the aggregateto reveal trends when all manual or personal overrides are consideredover a period of time. Based on logged temperature data over a period oftime, heat maps for commissioned units may be created and overheatedcommissioned units and under-heated commissioned units may beidentified. Because temperatures in one zone may affect the temperaturein adjacent zones, some zones may be over or under heated based on thetemperature in adjacent zones. Analysis of logged temperature data mayreveal such trends. Mathematical models may then be used to suggestchanges in temperature and air flow parameters for commissioned units inorder to counteract any identified negative trends.

Recording and Presenting Maintenance-Related Data

All monitoring data that relates to maintaining the system in workingcondition may be presented on one or more related user interfaces. Inmany embodiments, these UIs (presented as one or more windows, panels,or linked websites) present data such as diagnostic messages; alarms,warnings, and other events associated with commissioned units; emergencylighting activations; reports and notifications on device failures; andplanned and completed device replacements. Unlike an alarm, whichsignifies that a device may not be operating as intended, a warningsignifies that the system may be running near or outside its operatingbounds (e.g. signifying a device nearing end of life, overvoltage orovercurrent circumstances). Different visual characteristics (e.g.different icons and colors) may be used to visually indicate differentcategories of device malfunction, such as communication failure and lackof power.

In some embodiments, when a faulty device or commissioned unit isreplaced, a user with appropriate maintenance credentials may use theCentral Dashboard to re-commission the device in accordance with themethod depicted in FIG. 5. The replaced device may be discovered by thesystem and its location marked on the floor plan. Commissioning dataabout the device involved may be shared between system modules such ascommissioning module 120 and environment manager module 110 in order toeffectively re-commission a device after replacement. The process ofbinding a replaced device to sensors may be begun, for example, by anauthorized user simply dragging and dropping an icon representing thediscovered device onto icons representing one or more sensors on thedigital floor plan displayed by the Central Dashboard.

System modules such as environment manager module 110 may performsystem-wide or localized self-checks. The self-checks may be initiatedautomatically at regular intervals or manually by an authorized user.Reports and diagnostic messages may be generated by system modules orcommissioned units on the health of various commissioned units or systemmodules, and presented on the Central Dashboard. For manually-requestedself-checks, the system may provide feedback to the user on the progressof the self-check. Additionally, system modules may log and makeavailable TCP/IP network messages related to various commissioned units.

User-Management Dashboard

The Central Dashboard may also comprise a User-Management GUI thatallows an authorized user to create, edit and delete user accounts forusers of the system. The user accounts may be accounts for users of thestructure in question (e.g. office workers), as well as accounts for useby administrators with permissions to configure user accounts. Each userand administrator account may have an associated user ID and passwordfor authentication purposes. In some embodiments, administrator accountsare able to configure, for example: what types of data is monitored,which users are able to view the monitored data and at what granularity,which system parameters are configurable and which users are able toalter the values of such parameters, which users receive systemnotifications, and which commissioned units are used for varioussystem-level tasks (e.g. gathering monitoring data).

Aside from providing means for manually creating new user andadministrative accounts, the User-Management GUI may also facilitate thecreation of user accounts by importing previously existing user accountsfrom existing user account infrastructures (e.g. LDAP, RADIUS/activeserver). In some embodiments, user accounts may have an assigned role(e.g. the role of a maintenance engineer). All users assigned to acertain role may have the same level of access to information and thesame level of control over various aspects of the system. For example,all users assigned the role of maintenance engineer may be allowed toview at a certain level of detail or granularity, monitored usageinformation (e.g. illumination levels in various locations of thebuilding) pertinent to maintaining the system's functionality.Accordingly, a role may act as a template with certain permissions beingenabled and others being disabled. Assigning roles to user accounts isconsequently an efficient way to restrict users from accessingpotentially sensitive information about other users' activities withinthe structure in question, while still allowing users to access to theappropriate types of information for performing functions related totheir assigned roles.

The User-Management GUI may also allow for the creation and managementof customer accounts, where administrative and user accounts are eachassociated with a customer account. The system may support multiplecustomer accounts, such that administrator accounts for each customeraccount may be authorized to edit user accounts associated only with itsown customer account. Such an arrangement allows for the management ofenvironmental conditions in the same physical space by separateentities. For example, the same office building may be occupied by oneentity from Monday through Wednesdays and another entity on Thursdaysand Fridays. Each entity may have a different customer account with useraccounts associated with its own employees.

Maintenance and Reliability

Software Upgrades

System modules (e.g. environment manager module 110 or gateway module130) may, in various embodiments, allow software upgrades ofcommissioned units. During various stages of the software upgradeprocess, devices undergoing the upgrade may not be operational. Softwareupgrades may be conducted on a scheduled basis, they may be startedremotely using user interfaces such as the Central Dashboard, or on-siteby a qualified user (e.g. field support engineer) using system toolssuch as the Commissioning tool. They may be conducted for select devicesor on a class of devices, and the Central Dashboard may reflecton-going, scheduled and completed software upgrades for commissioneddevices in the system.

During a software upgrade, the behavior of devices such as lightingdevices may be different from their configured behavior prior to theupgrade. For example, commissioned lighting units involved in a softwareupgrade and subsequent reboot may provide a particular level ofillumination (e.g. at a background level of illumination), and ignoreany lighting control requests that are received. System modules involvedin preparing and/or forwarding automatically or manually-generatedenvironment control commands (e.g. environment manager module 110 orgateway module 130) to commissioned units may stop forwarding thecommands to commissioned units that are presently undergoing a softwareupgrade. After a software upgrade has been completed, the upgradeddevice may, in some embodiments, return to its behavior just prior tothe upgrade. In many embodiments, a software upgrade of a device doesnot overwrite or delete configuration parameters that were set prior tothe upgrade.

In many embodiments, to protect against security breaches, only approvedversions and types of firmware and computer code will be accepted bydevices for upgrade purposes, and only authorized users will be ableinitiate software upgrades. The transmittance of upgrade-related datafiles may only be permitted through secure communication channels.

The present inventors have realized and appreciated that in some caseswhen operating software upgrades are performed, issues such as bugs,incompatibilities, and the like could arise that would render a newlyupgraded luminaire controller (and its associated luminaire(s))unusable. This could include the luminaire(s) malfunctioning, or ceasingoperation altogether.

Furthermore, in many cases luminaire controllers are rather smalldevices with limited ROM/RAM storage capacities, and in general it maynot be possible to store a complete system restore point in memory inthe luminaire controller so that the luminaire controller could revertto its previously working state. Also, when a luminaire controller isupgraded, the new operating software may store new data and/or reformatdata (e.g., a configuration data set—further details and examples ofconfiguration data will be provided below) in memory in the luminaire insuch a way that the previous version of the operating software is nolonger usable even if it could be stored in the luminaire and restored.

Under such circumstances, simply reverting to the previous operatingsoftware may not be possible or may not solve the problem.

For example, consider a case where a luminaire controller is operatingwith Software Version A and corresponding Configuration Data Set A, andthe luminaire controller is upgraded to Software Version B andcorresponding Configuration Data Set B. If, after upgrade, the luminairecontroller does not function as expected or desired, one might decide torevert to Software Version A. However, even if Software Version A isstill present in the memory of the luminaire controller, upon reversionthe luminaire controller will have Software Version A and ConfigurationData Set B—which may be totally incompatible with each other. Forexample, the format of Configuration Data Set B may be different fromthat which Software Version A is expecting and was designed to operatewith.

Toward this end, the present inventors have conceived and developed asystem and method for a luminaire controller to autonomously create arestore point and save its configuration data set such that if an issuearises which negatively affects the functioning of the luminairecontroller after an operating software upgrade, the luminaire controllermay autonomously restore itself to a previously working state.Embodiments of such a system and method will now be described withrespect to FIGS. 28-34.

FIG. 28 illustrates an example embodiment of an illumination system2800, or lighting network, including a luminaire controller 2810connected by a communication network 2805 to first and second devices2820 and 2830.

Luminaire controller 2810 controls one or more luminaires 2802, each ofwhich may include one of more light sources (e.g., LED light sources).Luminaire controller 2810 includes a processor 2812 and memory 2814.Memory 2814 may include a plurality of memory elements. In variousembodiments, memory 2814 includes at least one nonvolatile memoryelement, which may include one or more of: a programmable read onlymemory, a FLASH memory, a magnetoresistive RAM (MRAM), a ferroelectricRAM (F-RAM), and the like. Luminaire controller 2810 may in generalinclude a number of other components, such as a communication interfacefor communication network 2805, which are not shown in FIG. 28 orspecifically described herein.

Processor 2812 of luminaire controller 2810 executes first operatingsoftware to perform its operations, including controlling operations ofone or more associated luminaires 2802. Memory 2812 stores a firstsoftware image 28000 of the first operating software. In particular,luminaire controller 2810 employs the first operating software tocontrol its associated luminaire(s) 2802, in conjunction with a firstconfiguration data set 28100 for the luminaire(s) which is also storedin memory 2814.

In general configuration data can include any data which is used toconfigure luminaire controller 2810 and/or the luminaire(s) 2802 whichit controls. Examples of configuration data which may be included inconfiguration data set 28100 include but are not limited to:communication parameters, metrics to be recorded and/or reported,luminaire configuration parameters, and luminaire illuminationparameters. Examples of communication parameters include but are notlimited to: an Internet Protocol (IP) address of the gateway controllerwith which the luminaire controller communicates, a Domain Name Server(DNS) address with which the luminaire controller communicates; anetwork ID of the luminaire controller; addresses of devices (e.g.,sensors; luminaires) with which the luminaire controller interacts; andan address where the luminaire controller should report its metric data.Examples of luminaire configuration parameters include a luminaire type,a luminaire's manufacturer, a luminaire's manufacture date (e.g., year,week, month, etc.). Examples of luminaire illumination parametersinclude: a type or version of lighting control algorithm employed by theluminaire controller to control the luminaire; parameters forconfiguring the luminaire to have a constant light output over time;etc.

First and second devices 2820 and 2830 are configured to store softwareimages and configuration data sets for restore points for luminairecontroller 2810. In particular, luminaire controller 2810 communicatesfirst software image 28000 via communication network 2805 to firstdevice 2820 which stores first software image 28000 in memory 2822.Also, luminaire controller 2810 communicates first configuration dataset 28100 via communication network 2805 to second device 2830 whichstores first configuration data set 28100 in memory 2832. In someembodiments, second device 2820 may be eliminated, and first device maystore both first software image 28000 and first configuration data set28100. In some embodiments, one or both of first and second devices 2820and 2830 may be a gateway controller for a lighting network in whichluminaire controller 2810 is deployed.

As will be described in greater detail below, when an operating softwareupgrade is desired for luminaire controller 2810, a second softwareimage for second (e.g., upgraded) operating software may be communicatedto luminaire controller 2810 via communication network 2805. In thatcase, luminaire controller 2810 may replace first software image 28000in memory 2814 with the second software image for second (e.g.,upgraded) operating software. However, first software image 28000remains stored in memory 2822 of first device 2820. Also, in the eventthat a second configuration data set is communicated to luminairecontroller 2810 as part of the upgrade, first configuration data set28100 remains stored in memory 2832 of second device 2830. Accordingly,if it is determined (for example during a self test) that the second(e.g., upgraded) operating software causes luminaire controller 2810and/or one of its associated luminaires to malfunction, or not functionat all, then luminaire controller 2810 may retrieve first software image28000 from first device 2820 and first configuration data set 28100 fromsecond device 2830, and may revert to the previously known functionaloperating state of first operating software and first configuration dataset 28100.

As will be described in greater detail below with respect to FIGS. 29and 30, the provision of first device 2820 and second device 2830 maypermit a plurality of previously-known good software images and/orconfigurations for a plurality of different luminaire controllers to bestored in one place. In that case, storage efficiencies may be obtained.For example, in some cases the software image for the operating softwarecorresponding to the last previously known good state may be the samefor a plurality of different luminaire controllers. In that case, onlyone copy of that software image needs to be stored (e.g., in firstdevice 2820). An index, or mapping table, also stored in first device2820 could be employed to keep track of which software images pertain towhich luminaire controllers.

FIG. 29 illustrates another example embodiment of an illumination system2900, or lighting network, including first and second luminairecontrollers 2810-1 and 2810-2 which are each connected via communicationnetwork 2805 to first and second devices 2820 and 2830.

First and second luminaire controllers 2810-1 and 2810-2 have generallythe same configuration and operation as luminaire controller 2810 asdescribed above with respect to FIG. 28 and only differences will bedescribed. Here, first luminaire controller 2810-1 is configuredaccording to first configuration data set 28100, and second luminairecontroller 2810-2 is configured according to a second configuration dataset 28102 which is different from first configuration data set 28100. Insome cases, first and second configuration data sets 28100 and 28102 mayhave a same format and version as each other, but may contain thereindifferent configuration data unique to the corresponding luminairecontroller 2810-1 or 2810-2.

As shown in FIG. 29, second luminaire controller 2810-2 communicatessecond configuration data set 28102 to second device 2830 viacommunication network 2805. Second device 2830 stores secondconfiguration data set 28102 in memory 2832. In some embodiments, memory2832 may also store an index or mapping table which identifies where theconfiguration data set for each different luminaire controller is storedin memory 2832. In some embodiments, memory 2832 may have fixed memoryaddresses assigned to each luminaire controller for which it stores aconfiguration data set.

In illumination system 2900, each of first and second luminairecontrollers 2810-1 and 2810-2 has the same known good operating softwareas each other, and accordingly only one software image 28000 is storedin memory 2822 of first device 2820 for both first and second luminairecontrollers 2810-1 and 2810-2.

FIG. 30 illustrates another example embodiment of an illumination system3000, or lighting network, including three luminaire controllers 2810-1,2810-2 and 2810-3 which are each connected via communication network2805 to first and second devices 2820 and 2830.

First, second, and third luminaire controllers 2810-1, 2810-2 and 2810-3have the same configuration and operation as described above withrespect to FIG. 29. Here, third luminaire controller 2810-3 isconfigured according to third configuration data set 28104 which isdifferent from first configuration data set 28100 and secondconfiguration data set 28102. In some cases, first, second and thirdconfiguration data sets 28110, 28102 and 28104 may have a same formatand version as each other, but may contain therein differentconfiguration data unique to the corresponding luminaire controller2810-1, 2810-2 or 2810-3.

As shown in FIG. 30, third luminaire controller 2810-3 communicatesthird configuration data set 28104 to second device 2830 viacommunication network 2805. Second device 2830 stores thirdconfiguration data set 28104 in memory 2832. In some embodiments, memory2832 may also store an index or mapping table which identifies where theconfiguration data set for each different luminaire controller is storedin memory 2832. In some embodiments, memory 2832 may have fixed memoryaddresses assigned to each luminaire controller for which it stores aconfiguration data set.

In illumination system 3000, each of first and second luminairecontrollers 2810-1 and 2810-2 has the same known good operating softwareas each other, and accordingly only one software image 28000 is storedin memory 2822 of first device 2820 for both first and second luminairecontrollers 2810-1 and 2810-2. However, third luminaire controller2810-3 has different known good operating software than the known goodoperating software for first and second luminaire controllers 2810-1 and2810-2. For example, third luminaire controller 2810-3 may be an oldermodel which is incompatible with the current version of operatingsoftware which is employed by first and second luminaire controllers2810-1 and 2810-2, and in that case third luminaire controller 2810-3may operate with a previous version of operating software which has asoftware image 28004. In that case, third luminaire controller 2810-3communicates software image 28002 to first device 2820 via communicationnetwork 2805. First device 2820 stores software image 28002 in memory2832, together with software image 28000. In some embodiments, memory2832 may also store an index or mapping table which identifies where thesoftware image for each different luminaire controller is stored inmemory 2822, or conversely which luminaire controllers pertain to eachdifferent software image stored in memory 2822.

A system and method for backing up or saving a known good restore pointfor a luminaire controller, and subsequently restoring the luminairecontroller to a known good operating state or condition using the savedrestore point, will now be described with respect to FIGS. 31-35.

FIG. 31 illustrates an example embodiment of an illumination system3100, or lighting network, during a normal operating mode.

Illumination system 3100 includes a plurality of luminaire controllers3110, including a first luminaire controller 3110-1, and a gatewaycontroller 3120, which are all connected by a communication network3105. Gateway controller 3120 includes a processor 3122 for controllingits operations, and a communication interface 3124. Gateway controller3120 also includes memory (not shown in FIG. 31) which may store one ormore software images and/or one or more configuration data sets, asdescribed above with respect to FIGS. 28-30.

Here, first luminaire controller 3110-1 is operating properly with firstoperating software SW1.

FIG. 32 illustrates an embodiment of illumination system 3100 during anoperating software upgrade where first luminaire controller 3110-1 hasreceived a new (second) software image for second operating software SW2from a luminaire programming apparatus 3200 which may be temporarilyconnected to communication network 3105. Here, programming apparatus3200 may be, for example, a laptop computer or a handheld computerdevice such as a tablet with a processor, memory, and a communicationinterface, wherein the processor executes an algorithm whereby itdistributes software upgrades or one, more than one, or all luminairecontrollers with which it is connected via communication network 3105.

In some cases or embodiments, when first luminaire controller 3110-1receives the new (second) software image for second operating software,it may also receive a second configuration data set with which secondoperating software operates to control operations of first luminairecontroller 3110-1.

FIG. 33 illustrates illumination system 3100 where first luminairecontroller 3110-1 which has received a new software image, stores acurrent (first) software image for the known good first operatingsoftware SW1, and a first configuration data set according to whichfirst luminaire controller 3110-1 is currently configured, to gatewaycontroller 3120. In some embodiments, the illumination system mayinclude a second device connected to communication network 3105 inaddition to gateway controller 3120. In that case, first luminairecontroller 3110-1 may communicate the first software image to one ofgateway controller 3200 and the second device, and may communicate thefirst configuration data set to the other of the gateway controller andthe second device, as described above with respect to FIGS. 28-30.

Although it is illustrated in FIGS. 32 and 33 that first luminairecontroller 3110-1 communicates the first software image and firstconfiguration data set to gateway controller 3120 after it receives thenew (second) software image, the order may be reversed. That is, in someembodiments, first luminaire controller 3110-1 may communicate the firstsoftware image and first configuration data set to gateway controller3120 at any time after it has determined that this corresponds to a goodworking state for first luminaire controller 3110-1 but before itreceives the new (second) software image.

FIG. 34 illustrates illumination system 3100 where first luminairecontroller 3110-1, which has received the new (second) software image,fails a self test after installing an operating software upgrade tosecond operating software SW2. In particular, after first luminairecontroller 3110-1 has received the new (second) software image (and insome embodiments a second configuration data set), it installs thesecond (upgraded) operating software SW2, saves the second configurationdata set in its memory, and begins operations. At some point afterinstalling second operating software SW2, first luminaire controller3110-1 performs a health check or self test to determine whether or notit is functioning properly or as expected with the new (upgraded)operating software SW2.

The self test may be performed in a variety of different ways. In someembodiments, a self test may simply be a counter which keeps track of anumber of times that the processor of first luminaire controller 3110-1has to perform a reboot due to some error within a specified timeinterval. For example, in some embodiments first luminaire controller3110-1 may fail a self test if first luminaire controller 3110-1 has toperform 10 reboots within a time period of 500 hours (of course, othernumbers could be used). In some embodiments, a self test may be a checkof the available stack size and queue size of all tasks being performedby the processor of first luminaire controller 3110-1, and when one orboth of these numbers exceed a threshold, then it may be determined thatthe self test has failed. In some embodiments, the processor of firstluminaire controller 3110-1 may execute a built-in algorithm in secondoperating software SW2 to check content in the configuration data setagainst expected characteristics to see if the data matched what isexpected. For example, the second operating software SW2 could check amodel or version number of a luminaire or sensor with which firstluminaire controller 3110-1 is connected to operate and verify whetherthe models or versions are supported by the upgraded second operatingsoftware SW2.

From the above descriptions it should be apparent that in variousembodiments the self test could include a discrete testing event and/oran ongoing continual health check of first luminaire controller 3110-1.

FIG. 35 illustrates illumination system 3100 where luminaire controller3110-1 has reverted to its previous software image and configurationdata set. Here, first luminaire controller 3110-1 has issued a requestfor gateway controller 3120 to transmit the first software image and thefirst configuration data set back to first luminaire controller 3110-1via communication network 3105. Upon receiving the first software imageand first configuration data set, first luminaire controller 3110-1stores the first configuration data set in it memory, and installs thefirst operating software using the first software image retrieved fromgateway controller 3120. In this state, illumination system 3100 nowoperates as shown in FIG. 31 above.

FIG. 36 illustrates a flowchart of an example embodiment of a method3600 of autonomously creating a restore point for a luminaire andautonomously restoring the luminaire to a working state when itmalfunctions after a software upgrade. In various embodiments, method3600 may be applied to illumination systems 2800, 2900, 3000 and 3100described above.

In an operation 3605, a luminaire operates using first operatingsoftware and first configuration data.

In an operation 3610, the luminaire receives a second software image forsecond (e.g., upgraded) operating software, and a second configurationdata set different from the first configuration data set, via acommunication network to which the luminaire is connected.

In an operation 3615, the luminaire copies a first software image forthe first operating software, and the first configuration data set, bytransmitting the first software image and the first configuration dataset to one or more devices to which the luminaire is connected by thecommunication network. For example, in some embodiments the firstsoftware image is copied to a memory in a first device, and the firstconfiguration data set is copied to a memory in a second device.

It should be understood that the order of operations 3610 and 3615 maybe reversed compared to that shown in the flowchart of FIG. 36.

In an operation 3620, the luminaire installs the second operatingsoftware using the second software image, and saves or stores the secondconfiguration data set in its memory.

In an operation 3625, the luminaire performs a self test, for example asdescribed above with respect to FIG. 34.

In operation 3630, it is determined whether the self test passed orfailed.

If the self test in operation 3625 fails, then the process proceeds tooperation 3635. In operation 3635, the luminaire requests that thedevice(s) where the first software image and first configuration dataset are stored transmits the first software image and the firstconfiguration data set back to the luminaire via the communicationnetwork.

In an operation 3640, the luminaire receives the first software imageand the first configuration data set.

In an operation 3645, the luminaire installs the first operatingsoftware using the retrieved first software image, and saves or storesthe retrieved first configuration data set in its memory.

If the self test in operation 3625 passes, then the process proceeds tooperation 3650, wherein the luminaire operates using the secondoperating software and the second configuration data set.

Maintenance: Re-Commissioning and Re-Configuration of Devices

Floor Map and Hot Plugging

In some embodiments, the commissioning tool provides an interactivefloor map depicting the actual physical placement of devices such assensors, PoE switches, luminaires, area controllers and gateway modules.During hot-plugging and hot un-plugging of such devices, (e.g. placementand removal of devices while the overall system is powered andoperational), the floor map may reflect, in real-time, the removal andaddition of devices.

Automatic Re-Commissioning: Luminaire and Sensor Replacement

In some embodiments, re-commissioning and re-configuring of a previouslycommissioned unit such as a luminaire or sensor after it is replaced maybe automatic. A report with details regarding the replacementcommissioned unit, the replaced unit and/or any errors or warningsresulting from the re-commissioning and/or re-configuring process maythereafter be created and forwarded to the Central Dashboard. The reportmay comprise the device and location where the exchange took place. Inmany embodiments, a replaced luminaire may resume its behavior as partof a commissioned unit within 5 seconds from the moment of connecting topower and communication lines.

Sensors, like other commissioned units, are also upgradable andreplaceable while the system is operational. For example, one or morecarbon dioxide, humidity and temperature sensors may be added even afterthe system has been commissioned and is operational. In manyembodiments, system modules such as the environment manager module 110or the gateway module 130 may recognize a replacement sensor'scapabilities and automatically commission the sensor by linking it to anappropriate commissioned unit. Additionally, the replacement sensor'scapabilities may be reported to the Central Dashboard.

Semi-Automatic Re-Commissioning:

In many embodiments, when a lighting system controller or actuatordevice is replaced (sensor, luminaire, control UI, area controller), anauthorized system user (e.g. commissioning engineer) may need tocommission and configure the device to enable proper functioning. Inmany cases, this may be achieved using the commissioning tool. In someinstances, when a commissioned unit is replaced, a system module such asthe environment manager module 110 or gateway module 130 may discoverthe device on the network and present the device for commissioning onthe commissioning tool.

Localizing a replaced device may be performed automatically, orsemi-automatically, where an authorized user (e.g. commissioningengineer) is asked for confirmation of a successful localization. Incase a single device is replaced in the system, the commissioning modulemay automatically re-configure the device with the configuration detailsof the malfunctioning one it replaced. An authorized user may also beable to request the latest version of the configuration data associatedwith the replaced device using, for example, the Central Dashboard.

Manual Re-Commissioning

An authorized user may use the Central Dashboard to manuallyre-commission commissioned units, and to re-configure parameters ofselected commissioned units. For example, a user may select devices foradding to a commissioned unit or split a commissioned unit intosub-units, and specify various parameters used to control the behaviorof the new commissioned unit(s).

Emergency Mode and Lighting

In situations where there is a power outage, or an un-switched mainsline is switched off, the system may activate a system-wide emergencymode. During the emergency mode, commissioned units may not react to anydaylight-based or occupancy-based controls, or to any control requestsfrom individual users. In various embodiments, emergency luminaires orlighting units dispersed throughout the structure may be activated toproduce sufficient light for purposes such as building evacuation. Suchemergency luminaires may each have one or more indicator LEDs, withvarious light states indicating related system states. For example, apermanent green light may indicate that the system is functioning asrequired; a blinking green light may indicate that the system isperforming a function or duration test; and a blinking red light with afour blink period may indicate battery failure.

Reliability

Light Output Quality

In some embodiments, luminaires of different light effect (e.g.temperature and color) may be used, and the system may support lightingdevices with the following specifications: Ra greater than 80;Uniformity for Task Lighting greater than 0.7; Uniformity for BackgroundLighting greater than 0.4; UGR (Unified Glare Rating) of 19 for officespaces, and 28 for circulation areas; and CCT of 4000K.

Network Failure

In situations where there is no network connectivity availablesystem-wide, the system may behave in a predetermined way until networkconnectivity has been reestablished. For example, occupancy-basedcontrols may be available in a limited capacity, to provide a minimumlevel of illumination in areas where occupancy is detected; anddaylight-based control and personal controls may be unavailable. Insituations where an individual luminaire or lighting unit detects thatit is no longer connected to the network, it may also behave in aprescribed way. For example, it may continue to provide the same levelof illumination as before the network failure was detected, and if it isswitched off, it may switch to providing a minimum level of illuminationif occupancy is subsequently detected in its vicinity. Such behaviorensures that even in the event of network failure, a minimum level ofillumination will be present in areas that are occupied.

PoE Switch Failure

FIG. 22 depicts an arrangement of commissioned units and associated PoEswitches for reducing the visual impact of PoE switch failure. In FIG.22, two PoE switches (PoE Switch A and PoE Switch B) are shown supplyingpower to multiple commissioned units, identified using dottedrectangles, in two separate rooms. PoE Switch A is shown as supplyingpower to three commissioned units and their respective luminaires orlighting units (shown as circles within the dotted rectangles) in Room 1and one commissioned unit and its luminaires in Room 2. PoE switch B isshown as supplying power to two commissioned units and their respectiveluminaires (or lighting units) in Room 2 and one commissioned unit andits luminaires (or lighting units) in Room 1. In such an arrangement,where each PoE Switch supplies power to at least one commissioned unitin each of the two rooms, neither room will be in complete darkness ifone of the PoE switches fails.

Self-Diagnostics

FIG. 23 illustrates a method 2300 for self-diagnosis and recoveryperformed by commissioned units in some embodiments of a system formanaging environmental conditions. FIG. 23 comprises steps 2310 through2350. In some variations of the method 2300, all the depicted steps neednot be performed in the order shown, one or more steps may be added to,and one or more steps may be deleted from the steps shown. In step 2710,a commissioned unit detects a defect in its own operation, with orwithout the aid of system modules such as gateway module 130. A defectmay be the inability of the commissioned unit to respond to a requestedcontrol command when the request is within the technical bounds allowedby its specification. For example, a defect may be a luminaire (orlighting unit or light source) not being able to provide lighting at aparticular level of illumination when its specification permits such alevel of illumination. Once the commissioned unit has detected thedefect, control transfers to step 2320. In step 2320, the commissionedunit attempt self recovery. Self recovery may involve the unitrestarting itself and/or otherwise resetting itself. Some commissionedunits may also be configured to attempt a series of other operationscommonly known to fix operational errors if a restart or reset does notfix the defect. Once the commissioned unit has attempted self recovery,the commissioned unit proceeds to step 2330, where the commissionedunit, with or without the aid of system modules such as gateway module130, checks to see if the detected defect is fixed. During this step,the commissioned unit may attempt to perform the same task thatpreviously caused it to detect the defect. If the defect is fixed, thecommissioned unit proceeds to function as usual and control transfersback to step 2310. In some embodiments, the commissioned unit may reportthe operational error to another system module such as the environmentmanager module 110, commissioning module 120 or gateway module 130,while also conveying the message that the commissioned unit hasself-recovered from the error. Such an error report may not result incorrective action from the system modules notified, but may be used forstatistical purposes (e.g. recording system-wide operational errors andhow they were handled).

If the defect is not fixed, then control proceeds to step 2340 and thecommissioned unit reports the error to another system module (e.g.environment manager module 110, commissioning module 120 or gatewaymodule 130). The error report may have an urgency level associated withit, which may be set by the commissioned unit itself. The urgency levelmay influence how and when the module notified responds to the error.When reporting the error, the commissioned unit may also transmitinformation identifying itself to the module(s) it reports the error to.In response to the error report, one of the modules receiving the errorreport may respond by sending self-recovery instructions to thecommissioned unit. The self-recovery instructions may be, for example,computer code, or information identifying the location in, one or morememories, of computer code or instructions for self-recovery. In someembodiments, a system module such as the environment manager module 110may send a known bug fix in the form of computer code executable by thecommissioned unit if the reported error relates to a known bugassociated with the commissioned unit. In step 2350, the commissionedunit checks to determine if self-recovery instructions were received. Ifno instructions were received, control remains in step 2350, and thecommissioned unit awaits receipt of such instructions or other action byan authorized system user, such as a hardware replacement. Ifself-recovery instructions are received, then control transfers back tostep 2320, in which the commissioned unit attempts self recovery usingthe newly received instructions.

FIG. 24 illustrates an embodiment of an interactive graphical userinterface displayed as a front end to an environment manager module, inaccordance with some embodiments of a system for managing environmentalconditions. It depicts devices and commissioned units on an interactivefloor plan and, when requested, depicts usage information (e.g. burnhours, energy usage) and status information for these devices and units.FIG. 25 illustrates an embodiment of an interactive graphical userinterface displayed as a front end to a commissioning module, inaccordance with some embodiments of a system for managing environmentalconditions. The user interface allows a user to manually adjust, forexample, light levels of various lighting units in an area such as acell office. FIG. 26 illustrates an embodiment of an interactive areawizard for use as part of a front end to a commissioning module, thearea wizard permitting a user to specify various parameters thattogether define the function(s) of an area within a physical structure.Information received from the user with respect to the functions(s) ofan area may thereafter be used to automatically configure variousdevices inside the area. FIG. 27 illustrates an embodiment of aninteractive graphical user interface for use in commissioning a newdevice (e.g. a sensor) for use in a system for managing environmentalconditions.

While several inventive embodiments have been described and illustratedherein, those of ordinary skill in the art will readily envision avariety of other means and/or structures for performing the functionand/or obtaining the results and/or one or more of the advantagesdescribed herein, and each of such variations and/or modifications isdeemed to be within the scope of the inventive embodiments describedherein. More generally, those skilled in the art will readily appreciatethat all parameters, dimensions, materials, and configurations describedherein are meant to be exemplary and that the actual parameters,dimensions, materials, and/or configurations will depend upon thespecific application or applications for which the inventive teachingsis/are used. Those skilled in the art will recognize, or be able toascertain using no more than routine experimentation, many equivalentsto the specific inventive embodiments described herein. It is,therefore, to be understood that the foregoing embodiments are presentedby way of example only and that, within the scope of the appended claimsand equivalents thereto, inventive embodiments may be practicedotherwise than as specifically described and claimed. Inventiveembodiments of the present disclosure are directed to each individualfeature, system, article, material, kit, and/or method described herein.In addition, any combination of two or more such features, systems,articles, materials, kits, and/or methods, if such features, systems,articles, materials, kits, and/or methods are not mutually inconsistent,is included within the inventive scope of the present disclosure.

All definitions, as defined and used herein, should be understood tocontrol over dictionary definitions, definitions in documentsincorporated by reference, and/or ordinary meanings of the definedterms.

The indefinite articles “a” and “an,” as used herein in thespecification and in the claims, unless clearly indicated to thecontrary, should be understood to mean “at least one.”

The phrase “and/or,” as used herein in the specification and in theclaims, should be understood to mean “either or both” of the elements soconjoined, i.e., elements that are conjunctively present in some casesand disjunctively present in other cases. Multiple elements listed with“and/or” should be construed in the same fashion, i.e., “one or more” ofthe elements so conjoined. Other elements may optionally be presentother than the elements specifically identified by the “and/or” clause,whether related or unrelated to those elements specifically identified.Thus, as a non-limiting example, a reference to “A and/or B”, when usedin conjunction with open-ended language such as “comprising” can refer,in one embodiment, to A only (optionally including elements other thanB); in another embodiment, to B only (optionally including elementsother than A); in yet another embodiment, to both A and B (optionallyincluding other elements); etc.

As used herein in the specification and in the claims, “or” should beunderstood to have the same meaning as “and/or” as defined above. Forexample, when separating items in a list, “or” or “and/or” shall beinterpreted as being inclusive, i.e., the inclusion of at least one, butalso including more than one, of a number or list of elements, and,optionally, additional unlisted items. Only terms clearly indicated tothe contrary, such as only one of or “exactly one of,” or, when used inthe claims, “consisting of,” will refer to the inclusion of exactly oneelement of a number or list of elements. In general, the term “or” asused herein shall only be interpreted as indicating exclusivealternatives (i.e. “one or the other but not both”) when preceded byterms of exclusivity, such as “either,” “one of,” “only one of,” or“exactly one of.” “Consisting essentially of,” when used in the claims,shall have its ordinary meaning as used in the field of patent law.

As used herein in the specification and in the claims, the phrase “atleast one,” in reference to a list of one or more elements, should beunderstood to mean at least one element selected from any one or more ofthe elements in the list of elements, but not necessarily including atleast one of each and every element specifically listed within the listof elements and not excluding any combinations of elements in the listof elements. This definition also allows that elements may optionally bepresent other than the elements specifically identified within the listof elements to which the phrase “at least one” refers, whether relatedor unrelated to those elements specifically identified. Thus, as anon-limiting example, “at least one of A and B” (or, equivalently, “atleast one of A or B,” or, equivalently “at least one of A and/or B”) canrefer, in one embodiment, to at least one, optionally including morethan one, A, with no B present (and optionally including elements otherthan B); in another embodiment, to at least one, optionally includingmore than one, B, with no A present (and optionally including elementsother than A); in yet another embodiment, to at least one, optionallyincluding more than one, A, and at least one, optionally including morethan one, B (and optionally including other elements); etc.

It should also be understood that, unless clearly indicated to thecontrary, in any methods claimed herein that include more than one stepor act, the order of the steps or acts of the method is not necessarilylimited to the order in which the steps or acts of the method arerecited.

Reference numerals appearing in the claims between parentheses areprovided merely for convenience in line with European patent practiceand should not be construed as limiting the claims in any way.

In the claims, as well as in the specification above, all transitionalphrases such as “comprising,” “including,” “carrying,” “having,”“containing,” “involving,” “holding,” “composed of,” and the like are tobe understood to be open-ended, i.e., to mean including but not limitedto. Only the transitional phrases “consisting of” and “consistingessentially of” shall be closed or semi-closed transitional phrases,respectively.

We claim:
 1. A method (3600), comprising: operating (3605) a luminairecontroller for a luminaire by executing first operating software havinga first software image; receiving (3610) at the luminaire controller, asecond software image of second operating software for the luminairecontroller; communicating (3615) the first software image of the firstoperating software to a first device connected to the luminairecontroller via a communication network; installing (3620) the secondoperating software at the luminaire controller; performing (3625) a selftest at the luminaire controller; and based on the results of the selftest, the luminaire controller: requesting (3635) that the first devicetransfer the first software image to the luminaire controller via thenetwork, installing (3645) the first operating software, and revertingto operation with the first operating software.
 2. The method (3600) ofclaim 1, further comprising: communicating (3615) a first configurationdata set for the luminaire controller from the luminaire controller to asecond device connected to the luminaire controller via thecommunication network; receiving (3610) at the luminaire controller asecond configuration data set for the luminaire controller; and uponfailure of the self test, the luminaire controller requesting (3635) viathe network that the second device transfer the first configuration dataset via the network to the luminaire controller.
 3. The method (3600) ofclaim 2, where the second configuration data set has a different formatthan the first configuration data set.
 4. The method (3600) of claim 1,wherein the luminaire controller receives (3610) the second softwareimage before communicating (3615) the first software image to the firstdevice.
 5. The method (3600) of claim 1, wherein the luminairecontroller performs the self test (3625) and verifies correct operation(3650) before the luminaire controller communicates the first softwareimage to the first device.
 6. The method (3600) of claim 1, wherein theluminaire controller communicates (3615) the first software image of thefirst operating software to the first device prior to receiving (3610)the second software image of the second operating software for theluminaire controller.
 7. A lighting system (2800, 2900, 3000, 3100)comprising: a first luminaire (2802); a first luminaire controller(2810-1, 3110-1) configured to control operations of the firstluminaire; at least one device (2820, 2830, 3120) including at least onememory (2822, 2832, 3122) storing at least a first software image(28000) for first operating software (SW1) which was previously employedby the first luminaire controller, and further storing therein a firstconfiguration data set (28100) according to which the first luminairecontroller was previously configured; a communication network (2805)communicatively connecting the first luminaire controller and the atleast one device, wherein the first luminaire controller includes atleast one memory (2814) storing: second operating software (SW2) that isdifferent from the first operating software, and that is employed by thefirst luminaire controller, and a second configuration data set (28100)that is different from the first configuration data set and according towhich the first luminaire controller is configured.
 8. The lightingsystem (2800, 2900, 3000, 3100) of claim 7, further comprising: a secondluminaire (2802) and a second luminaire controller (2810-2, 3110)connected to the communication network and configured to controloperations of the second luminaire, wherein the second luminairecontroller includes a memory (2814) storing the first operating software(SW1) and an additional configuration data set (28102) according towhich the second luminaire controller is configured, and wherein thememory of the at least one device further stores a further configurationdata set (28102) according to which the second luminaire controller waspreviously configured, the further configuration data set beingdifferent from the first configuration data set, the secondconfiguration data set, and the additional configuration data set. 9.The lighting system of (2800, 2900, 3000, 3100) claim 7, furthercomprising: a second luminaire (2802) and a second luminaire controller(2810-2, 3110) connected to the communication network and configured tocontrol operations of the second luminaire, wherein the second luminairecontroller includes a memory (2814) storing the second operatingsoftware (SW1) and an additional configuration data set (28102)according to which the second luminaire is configured, and wherein thememory of the at least one device further stores a further configurationdata set (28102) according to which the second luminaire controller waspreviously configured, the further configuration data set beingdifferent from the first configuration data set, the secondconfiguration data set, and the additional configuration data set. 10.The lighting system (2800, 2900, 3000, 3100) of claim 9, wherein the atleast one memory of the at least one device further stores a secondsoftware image (28002) for the second operating software.
 11. Thelighting system (2800, 2900, 3000, 3100) of claim 9, wherein the atleast one memory of the at least one device further stores an indexindicating which of the stored configuration data sets applies to thefirst luminaire controller and which of the stored configuration datasets applies to the second luminaire controller.
 12. The lighting system(2800, 2900, 3000, 3100) of claim 7, wherein the at least one deviceincluding the at least one memory includes a first device (2820) havinga first memory (2822) storing at least the first software image forfirst operating software previously employed by the first luminaire, anda second device (2830) having a second memory (2832) storing the firstconfiguration data set according to which the first luminaire controllerwas previously configured.
 13. A device (2820, 2830, 3120), comprising:a processor (3122); a communication interface (3124) configured forconnection to a communication network (2805, 3105) and configured tocommunicate with a plurality of luminaire controllers (2810, 3110) viathe communication network, wherein the luminaire controllers areconfigured to control operations of a plurality of luminaires (2802);and a memory (2822, 2832) configured to store at least one of: aplurality of configuration data sets (28100, 28102, 28104) according towhich various ones of the plurality of luminaire controllers werepreviously configured, and a plurality of software images (28000, 28002)for operating software according to which the various ones of theplurality of luminaire controllers previously operated.
 14. The device(2820, 2830, 3120) of claim 13, wherein the memory is further configuredto store at least one index which maps at least one of the plurality ofconfiguration data sets and the plurality of software images to thevarious ones of the plurality of luminaire controllers to which theycorrespond.
 15. The device (2820, 2830, 3120) of claim 13, wherein atleast one of the configuration data sets (28100, 28102, 28104) comprisesconfiguration data for at least one of the luminaire controllers, theconfiguration data including at least one of: an Internet Protocol (IP)address of a gateway controller with which the luminaire controllercommunicates; a domain name server (DNS) address of a device with whichthe luminaire controller communicates; a network ID of the luminairecontroller; an address of at least one sensor or luminaire with whichthe luminaire controller interacts; an address to which the luminairecontroller reports its metric data; at least one of a type,manufacturer, and date of manufacture of at least one luminaire whichthe luminaire controller interacts; a type or version of a lightingcontrol algorithm employed by the luminaire controller; and one or moreparameters employed by the luminaire controller for configuring aluminaire to have a constant light output over time.